Talk:Main Page

Main Page error reports

To report an error in content currently or imminently on the Main Page, use the appropriate section below.

• Where is the error? An exact quotation of the text in question helps.
• Offer a correction if possible.
• References are helpful, especially when reporting an obscure factual or grammatical error.
• Time zones. The Main Page runs on Coordinated Universal Time (UTC, currently 08:27 on 9 January 2024) and is not adjusted to your local time zone.
• Can you resolve the problem yourself? If the error lies primarily in the content of an article linked from the Main Page, fix the problem there before reporting it here. Text on the Main Page generally defers to the articles with bolded links. Upcoming content on the Main Page is usually only protected from editing beginning 24 hours before its scheduled appearance. Before that period, you can be bold and fix any issues yourself.
• Do not use {{edit fully-protected}} on this page, which will not get a faster response. It is unnecessary, because this page is not protected, and causes display problems. (See the bottom of this revision for an example.)
• No chit-chat. Lengthy discussions should be moved to a suitable location elsewhere, such as the talk page of the relevant article or project.
• Respect other editors. Another user wrote the text you want changed, or reported an issue they see in something you wrote. Everyone's goal should be producing the best Main Page possible. The compressed time frame of the Main Page means sometimes action must be taken before there has been time for everyone to comment. Be civil to fellow users.
• Reports are removed when resolved. Once an error has been addressed, determined not to be an error, or the item has rotated off the Main Page, the report will be removed from this page. Check the revision history for a record of any discussion or action taken; no archives are kept.

Administrators: Clear all reports

Errors in the summary of the featured article

Please do not remove this invisible timestamp. See WT:ERRORS and WP:SUBSCRIBE. - Dank (push to talk) 01:24, 29 September 2022 (UTC)

Errors in "Did you know ..."

Current DYK

• " ... that Kathanar – The Wild Sorcerer is being shot on a custom-built studio spanning 45,000 square feet, utilizing the virtual production technology?"

• The hook is sourced to an article that appears to be a paid advertorial which basically regurgitates the director's social media posts (even the headline is a straight copy of his quote) - the TOI is notorious for this sort of thing. Also, it's undersourced; there are unsourced statements in the main Production paragraph, and only one of the cast has a citation as well.

• @AirshipJungleman29, Launchballer, and Jupitus Smart: Black Kite (talk) 18:28, 8 January 2024 (UTC)

That hook also appeared in Cinema Express, with which I have no problems.--Launchballer 18:44, 8 January 2024 (UTC)

That would be fine, except that source only says "Major portions of the film have been planned to be shot on a massive 45,000 square feet modular shooting floor." Black Kite (talk) 18:56, 8 January 2024 (UTC)

I've added sources for the cast. Launchballer, going forward, I suggest that you should have requested tighter sourcing before signing off on nominations that look a bit thinly referenced. Schwede66 23:57, 8 January 2024 (UTC)

Hope They'll Fix This 103.212.141.29 (talk) 06:24, 9 January 2024 (UTC)

Errors in the summary of the featured list

Friday's FL

(January 12)

Monday's FL

(January 15)

Errors in the summary of the featured picture

Notice to administrators: When fixing POTD errors, please update the corresponding regular version (i.e. without "protected" in the page title) in addition to the Main Page version linked below.

General discussion

Edit request - Less of a short-term solution

Please replace lines 127-131 of Wikipedia:Main Page/styles.css with the following:

	#mp-tfp tr:first-child td:first-child a.mw-file-description {
		text-align: center;
		display: table;
		margin: 0 auto;
	}

Reason: Earlier today, the display: table declaration was commented out, as this was preventing mobile viewers from playing the Steamboat Willie video. Looking at Wikipedia:Main Page/Tomorrow on a landscape-oriented mobile device, it appears that this CSS block was responsible for horizontally centering the image on the screen. I therefore propose reinstating the declaration, but changing the selector to be more specific - targeting a.mw-file-description rather than just a. (Image <a> tags generated by MediaWiki appear to have this class, while video <a> tags appear to instead have .mw-tmh-play.)

As with last time, if this breaks anything, the change can always be reverted (and/or the styles.css file restored to the version before today's change, provided the video is no longer on the Main Page at that point). The proposed changes are currently live in my sandbox (with my sandboxed TemplateStyles) with tomorrow's POTD.

This isn't a permanent solution, as it doesn't solve the fact that (when the POTD is a video) the video is also not centred on mobile landscape (at a glance, this appears to be something that could be fixed via span.mw-tmh-player, although I'd want to do more checks to be sure of that). However, it's intended to be less of a short-term fix than the change made earlier, while reinstating the image centering.

Pinging Maxim for information, as you responded to the last edit request (though don't feel obliged to also answer this one!). Also pinging Izno, as you've made a lot of the past changes to the Main Page's styles.

Let me know if there are any queries. All the best, ‍—‍a smart kitten_[meow] 18:18, 1 January 2024 (UTC)

 Done Izno (talk) 19:10, 5 January 2024 (UTC)

This area needs fixing anyway, so this change effectively restores the hack but slightly more selective to imagery rather than video, as mentioned above. Izno (talk) 19:11, 5 January 2024 (UTC)

Today's main page balance

On a wide screen, the main page is perfectly balanced. On a narrow screen, it's totally out of kilter. On my phone, the ODT footer lines up with bottom of the fourth DYK hook, i.e. there are four more DYKs below that. Anyone got an idea what to do about it? Schwede66 08:29, 7 January 2024 (UTC)

Firstly, is this using the Vector 2022 skin? My assumption is that we should always optimise for that rather than legacy Vector, because it's the reader default, even if many editors have switched back. And secondly, I'm not sure it's possible to optimise the main page desktop view for display on a phone - there are so many different screen widths out there and mobile browsers probably make different decisions about how to render the page in a very narrow form factor. On my phone, the bottom of OTD is currently lined up with the penultimate DYK hook, which is OK given that I don't particularly expect it to render accurately on the phone...  — Amakuru (talk) 08:50, 7 January 2024 (UTC)

Yes, Vector 2022. Schwede66 14:01, 7 January 2024 (UTC)

It doesn't help that ITN and OTD are rendered on mobile with a smaller font size than TFA and DYK. Not sure where that was decided? Stephen 09:34, 7 January 2024 (UTC)

If we just went with a single column Main Page (like every other page), this would instantly cease to ever be a problem. --User:Khajidha (talk) (contributions) 16:31, 8 January 2024 (UTC)