Wikipedia:Village pump (technical)

After it virtually went away for a week or two I'm having the "randomly finding myself logged out when loading a page" thing happening again today. Five times in the last three and a half hours. As before one click logs me back in, but it's seriously annoying (especially when it happens when trying to upload things at Commons). - The Bushranger _{One ping only} 19:07, 9 April 2026 (UTC)

Next time this happens, before clicking "log in", open your browser console and type mw.config.get('wgRequestId'). You should see a UUID like like af059e2a-ea0f-4657-8b7e-c523e2ee0dcf. Paste it here, and maybe someone with a (WMF) account will be able see what's going on. Suffusion of Yellow (talk) 19:30, 9 April 2026 (UTC)

@Suffusion of Yellow this just happened to me again and I would love to be able to follow your instructions but I don't know even know what "browser console" is much less the other instructions. S0091 (talk) 20:07, 13 April 2026 (UTC)

@S0091: These directions assume desktop Firefox or Chrome/Chromium:

1. Wait until the next time this happens
2. While still on the "logged-out" page, open your developer tools by typing F12 or Ctrl+⇧ Shift+I. (If you forget these instructions, use another tab to visit WP:VPT...)
3. Click "Console"
4. At the > prompt, type mw.config.get('wgRequestId') and press ↵ Enter
5. You should see a UUID of the form "xxxx-xxxx-xxx-xxxxxxxxxxxx". This is an index into a log that some developers have access to.
6. Copy and past that here, along with a ping to Quiddity (WMF) and be prepared to answer any other questions.

Note: Don't, in general, make habit out of typing things in the console that random strangers on the Internet tell you to. If you don't trust me, ignore all this. Suffusion of Yellow (talk) 20:40, 14 April 2026 (UTC)

Same for me, and happening quite regularly. Fortunately pushing the submit edit button again logs me back in for the edit, but I'm having to hit it twice with every edit today. This is a regularly occurring (every week? two weeks?) issue this year and been a ripe pain in the arse since this seems to be defying my wishes to stay logged in on this device. I'm using Firefox (UTD) on a Windows11 laptop. If someone from WMF would find the UUID thing helpful, I've saved a few wgRequestId values on different attempted edits from this morning and willing to share via email with a verified WMF user. Zinnober9 (talk) 16:16, 15 April 2026 (UTC)

@Quiddity (WMF): You clicked "thank" on my previous message, so maybe you can help here? Suffusion of Yellow (talk) 18:48, 15 April 2026 (UTC)

@Suffusion of Yellow Yes, I can potentially help relay information. However, please clarify whether the wgRequestId UUID is at all private? I.e. You provided an example further above, and wrote "Paste it here" as instructions, so I believe that it is totally fine for anyone to share their wgRequestId values in this thread and/or public phabricator tasks. In which case, there's no need for Zinnober9/anyone to email me, they can just reply here which will help centralize the details that a dev needs to look at. [I tried to research the answer, but I cannot see requestID mentioned in mw:Manual:How to debug/Login problems for example.] Thanks. Quiddity (WMF) (talk) 19:16, 15 April 2026 (UTC)

@Quiddity (WMF): @Zinnober9: RequestIds of successful edits and other publicly logged actions are public; click "stream" at https://stream.wikimedia.org/v2/ui/#/?streams=recentchange to see a few. I can't think of any reason why sharing a non-editing RequestId would be a problem. Suffusion of Yellow (talk) 19:36, 15 April 2026 (UTC)

Oh. Unless you made an edit while logged out, and don't trust TAIVs with your IP. In that case, obviously, don't share anything about that specific edit, including the page, timestamp, request ID, etc. Suffusion of Yellow (talk) 19:40, 15 April 2026 (UTC)

@Quiddity (WMF): @Suffusion of Yellow: Ok, Was just being extra cautious. A "Trust, but verify" sort of thing. The two RequestIds I saved are "29189b60-4147-43a9-ab57-bbfe53804386" (attempted at Talk:Road safety/Archive 1) and "5ecf7e34-0ccc-4400-bb92-5e8f2dd769ed" (attempted at Talk:Rocky Brands/Archives/2014). If I encounter others today and you want more, I can add in a batch later or tomorrow. Thank you! Zinnober9 (talk) 20:11, 15 April 2026 (UTC)

Had more this morning.

"4c676076-abae-4382-a0f9-a48359230785"

"b5f083ad-1502-470b-85eb-f78743b8922c"

"af2f0088-f0e9-471b-b853-4f2da7bb5661"

"a4b46332-8ff7-4f75-9103-88331cce06e9"

"12270db6-6090-4cad-b627-2cdaf037dd8d"

"3053b448-ec05-49ad-9338-9266e7790823"

"bb6a5437-96db-4cfa-b3f1-08203fe628ed"

Had a dozen or more pages open at one time (I was chasing after one particular syntax error and had a few dozen pages remaining with it). Refreshing some of the pages I had open after I started running into this session logged out issue saved the edit fine on first submission, others that were refreshed did not and took the typical (for this issue) two submission attempts.

Zinnober9 (talk) 12:45, 17 April 2026 (UTC)

I did it @Suffusion of Yellow! Excellent instructions. It's "812f4f71-e3bc-4fb3-ac98-a38c57da1dfb". I was only logged into Wikipedia at the time of the log out and think I had about 7 tabs open. I did not have to log back in to post this so it appears it logged me back in automatically. My browser is Firefox and I am assuming the most recent version (it updated a couple-ish weeks ago). S0091 (talk) 16:49, 17 April 2026 (UTC)

Hi all, @Quiddity has asked me to have a look.

I looked up all of these request IDs, and we don't have any logs associated with them. That doesn't mean anything, though, since the request ID is just for the "primary" request of the page, while your session could have been invalidated by any of the sub-requests (e.g. styles, scripts, anything that gadgets do), a previous request, or a request in another browser tab.

WMF has detailed logs of session and authentication events (session loss errors, logins, autologins [the "one-click" ones], password changes, etc.), which we can look up by username, so there is no need to report request IDs for this problem. The request IDs are very useful for other issues where our logs don't include usernames (e.g. exceptions thrown by the software also display a request ID, so that someone can look up the details when you file a bug). They're safe to share in public.

I looked up the session logs for the three of you in the past week, and they don't indicate any obvious issues on our side. I don't want to share any details here since the logs include an uncomfortable amount of PII.

I have some questions which may narrow down the cause of the problems:

• Do you use the "Keep me logged in" option when logging in? (without it, logins are only supposed to last for 24 hours or until you close your browser, whichever is sooner)
• Do you use any login/authentication methods other than a password? (2FA, passkeys, etc.)
• What browser and operating system do you use, and do you use any privacy-enhancing browser settings or extensions?

Some hypotheses I have:

• If you're using Firefox, then this may be the same problem as T401554: Constantly getting logged out across projects on Firefox with 'Strict Enhanced Tracking Protection' enabled, or maybe some related change in latest Firefox versions. The mechanism we use to log you into all Wikimedia wikis (and enable the "one-click" logins if that fails) is very similar to the one used by ad networks to track you across websites, and your browser or some extension may be clearing the cookies for this reason.
• Otherwise, it could be the same problem T421168: Session store issues causing badtoken errors, session failures, logouts (late March–April 2026), which may be a problem on our side that started during the recent datacenter switch, but we haven't been able to investigate it yet.

-- Bartosz Dziewoński (WMF) / Matma Rex talk 22:45, 17 April 2026 (UTC)

@Bartosz Dziewoński (WMF), no, I do not use the Keep logged in option or any authentication. My browser is Firefox, op system Windows 11 and no privacy enhancing settings, etc. The only non-standing setting is to delete cookies after closing. This issue has been occurring to me for over a year (not sure how long) but very intermittent until recently. Other recent reports of this issue are here (March 11) and here (March 24). S0091 (talk) 14:34, 18 April 2026 (UTC)

Today I was logged out three times. What I've noticed is different from what I reported back during the March 24th discussion is refreshing the page does not work. I have to click "Log in" to get logged back in, though it does not require me re-enter my user id and password. S0091 (talk) 17:48, 18 April 2026 (UTC)

• Keep me logged in: Yes
• 2FA authentication etc.: No
• Firefox, up to date. Tracking Protection is set to "standard". I also have uBlock Origin and Ghostry addons, and have for multiple years, with no history of login issues. I did have one issue with uBlock earlier this week on another site where it was thinking that the site's header menus were a popup ad, but I've had this (Wikipedia logout) issue prior to this week, and the behaviors of that issue and this have no similarities, so I don't think there's any connection.
• T421168 sounds good, but I don't have the knowledge to judge it beyond the description of behavior. I have been thinking that my experience has behaved like a "you are logged in on serverA, but editing a page on serverB, and you are not logged in on serverB and we aren't going to log you in unless you ask us twice" sort of situation with a failed login handshake between the two servers since it shows me logged in in to upper right at all times and refuses the edit on first attempt, yet rerequesting the edit is accepted. But this is probably a gross oversimplification.

Zinnober9 (talk) 22:44, 18 April 2026 (UTC)

@Quiddity (WMF)@Matma Rex@Bartosz Dziewoński (WMF) I don't want this issue to get archived yet again. Can someone provide an update or at least an acknowledgment of the responses? Something. S0091 (talk) 20:16, 22 April 2026 (UTC)

I acknowledge and appreciate your responses, but I don't have anything new to say at the moment, sorry. Matma Rex talk 20:52, 22 April 2026 (UTC)

MediaWiki message delivery 20:41, 4 May 2026 (UTC)

Comment: "The number of available thumbnail size preferences in MediaWiki is being reduced" This is not true. My preferences set the thumbnail size to 300px, and they are now rendering at 220px. I tried lifting to 400px but no change. Also, the sizes in the Preferences are now 120, 150, 180, 200, 220, 250, 300 and 400. Hawkeye7 (discuss) 22:46, 5 May 2026 (UTC)

I had set my preferences to 220px, but now they are either rendering too small for my device as 180px or too large at 300px. There is no workable middle, and the CSS prompt they suggested here is not bypassing the change for every thumbail size. On my end, I am getting some too small and others too large concurrently. This is mildly infuriating. — Trailblazer¹⁰¹🔥 ^{(discuss · contribs)} 20:38, 6 May 2026 (UTC)

There is 250px too, the same size as the default. The way that the code is written in the software, you need to pick it specifically, the next size over will not change to it. Snævar (talk) 21:11, 6 May 2026 (UTC)

Mapping 300px to 400px is going to be a problem. 300px is currently the largest suggested image size in the lead of article, MOS:IMAGESZ. If this is happening then 300px needs to be mapped to the 250px thumb. -- LCU ActivelyDisinterested «@» °∆t° 18:04, 7 May 2026 (UTC)

Or does this only effect editors who have set a preference? -- LCU ActivelyDisinterested «@» °∆t° 18:05, 7 May 2026 (UTC)

I feel like the previous default of 220px should have been rounded up to a new default of 250px, instead of down to 180px. 180px is ridiculously small. I think users are poorly served by suddenly shrinking images on them rather than giving them a small size increase, and many will now have to scramble to find the option to change it. I assume that this also explains the issues I have been seeing with bizarrely small images on mobile, and faulty thumbnail rendering on Commons, over the last week or so. — Goszei (talk) 19:44, 7 May 2026 (UTC)

There was nothing inherently wrong with having 220px as the default. Rounding it up to 250px is a reasonable solution rather than shrinking it down so much. However, for those of us who want to retain 220px as the default, the process to opt out of these changes has not really been well articulated. I have attempted to rectify this in my CSS, but the single image thumbnails (when my preferences are at 220px) remain stuck at 180px in spite of using the suggested code (unless I am missing something). The communication about this change being implemented soon and its rollout drastically changing standard thumbnail sizes breaks longstanding article structures. The only instance where this does not have a major noticeable impact is with {{multiple images}}. When I have tried displaying images at 220px, some remain stuck at 180px or all at 250px. 250px is not a good universal middle ground for all devices, unlike 220px has been for years. — Trailblazer¹⁰¹🔥 ^{(discuss · contribs)} 20:28, 7 May 2026 (UTC)

Just for reference. The default image size was changed from 220 to 250 after a RFC in January 2024. The change was implemented in April 2025, after technical details were sorted out. -- LCU ActivelyDisinterested «@» °∆t° 22:26, 7 May 2026 (UTC)

Okay than. My only question remains, how would I be able to set it up so the thumbnails remain at 220px? I tried what they suggested in my CSS page but it doesn't work consistently, which may be a lack of understanding on my part. I just get some at 220px and others stuck at 180px. — Trailblazer¹⁰¹🔥 ^{(discuss · contribs)} 23:40, 7 May 2026 (UTC)

Based on feedback, I've updated the instructions to hopefully eliminate room for error. Hopefully they help you. Make sure to set your image size to 250px before deploying the change to your CSS page. Hope this helps. Feel free to ping me (or my volunteer account Jdlrobson) on your user talk page if you still need help setting this up. Jon (WMF) (talk) 01:22, 9 May 2026 (UTC)

This new approach has worked for me, thanks Jon! - adamstom97 (talk) 08:49, 9 May 2026 (UTC)

Yes, it works splendidly! Thank you for all your work and help, Jon! — Trailblazer¹⁰¹🔥 ^{(discuss · contribs)} 23:46, 9 May 2026 (UTC)

Jon (WMF)/Jdlrobson, is it possible for either of you to change the settings for me accordingly, please? As with Trailblazer101, I prefer the thumbnails to remain at 220px. Here is my CSS page. Kailash29792 (talk) 01:50, 23 May 2026 (UTC)

On pages like nl:Charles Darwin (at least in Vector legacy), the sidebar's links to Wikidata, Commons, Wikisource, Wikiquote and Wikispecies have small versions of the relevant project's icons—I presume through CSS. I find they aid navigation.

Could we do that on this project?

How could it be enabled on other projects, such as Wikispecies? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:34, 12 May 2026 (UTC)

@Pigsonthewing {{Sister project links}}? --Ahecht (TALK
PAGE) 19:56, 12 May 2026 (UTC)

This is a template in the article itself, while Andy is referring to the sidebar in the interface. Chaotic Enby (talk · contribs) 20:11, 12 May 2026 (UTC)

That's coming from their default-on gadget "Interprojectlinks" - see w:nl:Special:Gadgets for the JS/CSS. Quiddity (talk) 20:21, 12 May 2026 (UTC)

Thank you. So how do we get that here? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:12, 12 May 2026 (UTC)

This is the CSS:

li.commons,
.wb-otherproject-commons {
  background-image: url(//upload.wikimedia.org/wikipedia/commons/4/4a/Commons-logo.svg);
  background-size: 16px 22px;
}
li.wikispecies,
.wb-otherproject-species {
  background-image: url(//upload.wikimedia.org/wikipedia/commons/d/df/Wikispecies-logo.svg);
  background-size: 16px 19px;
}
li.wikidata,
.wb-otherproject-wikidata,
.wb-otherproject-wikibase-dataitem {
  background-image: url(//upload.wikimedia.org/wikipedia/commons/4/4a/Wikidata_Favicon_color.svg);
  background-size: 16px 16px;
}

I've only supplied three rules, being the ones used by nl:Ekster, but there will be a similar rule for each of the other WMF wikis. --Redrose64 🌹 (talk) 22:05, 12 May 2026 (UTC)

I don't think this .css actually does anything unless you also have the accompanying .js at nl:MediaWiki:Gadget-InterProjectLinks.js installed. These rules also aren't the full .css for the gadget. I think the .css and .js code are written specifically for Vector legacy; don't seem to do anything on Vector 2022 though maybe I just tried it incorrectly. – Scyrme (talk) 22:22, 12 May 2026 (UTC)

Vector 2022 does show them, but in the right-hand sidebar. --Redrose64 🌹 (talk) 22:33, 12 May 2026 (UTC)

Vector legacy shows them in the right-hand sidebar. That's where I was looking for them when I tried it here on ~enwiki where I use the default Vector 2022 theme. I probably just did it wrong. If you were able to get it working, could you explain how? – Scyrme (talk) 02:46, 13 May 2026 (UTC)

By default, the other project links on new vector are on the opposite side to old vector. Next to view history is a "Tools" dropdown, and at the bottom of that are the other project sitelinks. Snævar (talk) 16:29, 13 May 2026 (UTC)

@Scyrme: Regarding Vector legacy shows them in the right-hand sidebar. Vector legacy has no right-hand sidebar. Vector 2022 is the only skin with a sidebar on the right, and this is where the links concerned are displayed for that skin. I can't find the links in MinervaNeue skin. For all other skins (Cologne Blue, Modern, MonoBook, Timeless, Vector legacy), they are in the sidebar on the left. --Redrose64 🌹 (talk) 21:39, 13 May 2026 (UTC)

See de:User:Hgzh/css/vectorSisterprojectIcons.css for a similar way to implement the icons. Johannnes89 (talk) 22:01, 13 May 2026 (UTC)

Hgzh´s script one does not work as it tries to fetch blocked 15px icons. The icons, if they worked, would be displayed further to the right compared to the InterProjectLinks gadget. Snævar (talk) 12:54, 14 May 2026 (UTC)

Indeed I noticed that as well and asked them to make an update, it used to work. I also created phab:T426286 suggesting to add the icons per default to Vector 2022. Johannnes89 (talk) 19:02, 14 May 2026 (UTC)

I updated the snippet to use available icon sizes. hgzh 17:34, 15 May 2026 (UTC)

Possibly getting off-topic here, but Timeless, being a responsive skin, can have a right sidebar if your display is wide enough. It has one sidebar on the left on my 11" tablet and 13" laptop, and two sidebars (left and right) on my 27" monitor. ClaudineChionh (she/her · talk · email · global) 22:55, 13 May 2026 (UTC)

[Restored from archive]

The question remains—What needs to be done, to have this implemented on this project? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:04, 21 May 2026 (UTC)

Wikipedia:Gadget says ask an interface admin to install it. Seems like an agreed proposal to me. Snævar (talk) 12:27, 24 May 2026 (UTC)

Thank you. Requested at Wikipedia:Interface administrators' noticeboard#Sibling project icons in side bar. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:15, 24 May 2026 (UTC)

Done! I've added it as an opt-in gadget for now: while the consensus is to have it on by default, it could be good to have it opt-in for a few hours/days to make sure there aren't any glaring bugs I've overlooked. Please ping me either way! Chaotic Enby (in solidarity · talk · contribs) 17:59, 24 May 2026 (UTC)

Thank you.

Anyone wanting to test this should look for "InterProjectLinks" under Preferences/Gadgets. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:20, 24 May 2026 (UTC)

@Chaotic Enby I do not see consensus here and would expect several more editors to have commented in support for addition of a gadget. (I'm only not reverting you right now because it's off by default.) Izno (talk) 21:13, 24 May 2026 (UTC)

I support the gadget, jolly good thing. DuncanHill (talk) 21:20, 24 May 2026 (UTC)

...(using MonoBook) is that sometimes the "edit" links on the right-hand side of a section say "edit source" instead. Refreshing the page still has them saying "edit source", but they link to the regular edit function, function normally, and after editing the section the page post-edit has the usual "edit" links. Very weird - any idea what might be causing this? - The Bushranger _{One ping only} 22:20, 12 May 2026 (UTC)

I've noticed that, on certain user talk pages. I must remember to note which ones. I'm thinking there's some template or other in the top section that sets an unclosed <div class=...> --Redrose64 🌹 (talk) 22:35, 12 May 2026 (UTC)

Take a note of the pages you find this on. Also verify that you're using the old parser, not the new, at Prefs -> Editing -> Developer tools. Izno (talk) 04:34, 13 May 2026 (UTC)

Yes, old parser. Example where "[edit source]" links appear instead of "[edit]": Wikipedia:Featured article criteria. --Redrose64 🌹 (talk) 22:07, 14 May 2026 (UTC)

Ok. I see the same in old parser (and had caught it here and there). It displays as expected in Parsoid, at least for the wiki configuration we use. It's worth a bug report since there's at least one reproducible page. Izno (talk) 23:54, 14 May 2026 (UTC)

@Izno: Just came here after having that happen at ANI. Parser is "set to Wiki default". And having just gone back to ANI to check, it's back to just "edit"... - The Bushranger _{One ping only} 02:18, 16 May 2026 (UTC)

Also Wikipedia:General sanctions. --Redrose64 🌹 (talk) 08:16, 17 May 2026 (UTC)

It seems likely to me that this is some sort of caching issue, the effect of the VisualEditor "Editing mode" preference on the section edit links is being included in the cache without splitting the cache on the preference. Anomie⚔ 14:16, 17 May 2026 (UTC)

Experimenting seems to confirm this: If I change the preference, the edit links on Wikipedia:General sanctions stay as they were before. Then if I purge the page the links change to match the preference, and stay that way after changing the preference back until I purge again. As for "which cache?", I suspect it's the new-ish "post-processing cache" (aka "post-OutputTransform cache"). Anomie⚔ 15:27, 17 May 2026 (UTC)

Also VPT, as of immediately prior to this edit. Let's see if saving this post changes it... --Redrose64 🌹 (talk) 13:48, 20 May 2026 (UTC)

It did, so the issue is transient. --Redrose64 🌹 (talk) 13:49, 20 May 2026 (UTC)

I have my computer's theme set to dark so when I set the color setting to automatic, it switches me to dark mode. This mostly works fine but for some reason fails with userboxes. In addition to several userpages, the problem can be seen in TM:Userbox/doc#Examples. Using "automatic" results in white text on a white background but using "dark" results in readable userboxes. Warudo (talk) 01:08, 15 May 2026 (UTC)

This is somewhat expected. They were all written around 2007ish in a way that is not darkmode compatible. It requires fixes to almost every single one of them, but thats a lot of work and userboxes aren't as popular as they used to be and they aren’t content either so the priority and interest for fixing it hasn't been very high. —TheDJ (talk • contribs) 09:52, 15 May 2026 (UTC)

How on Earth is this expected? Automatic should be completely equivalent to either dark mode or light mode. But for some reason it is in this weird in-between state. Warudo (talk) 12:51, 15 May 2026 (UTC)

Last October, User:Jonesey95 made an edit to Template:Userbox/styles.css that overrode a manually set color with color: inherit; for the case where the OS preference is being followed, the background color is set, but the foreground color is not. As this change was not made for the case where dark mode is explicity selected, I suspect this is the problem. isaacl (talk) 16:53, 15 May 2026 (UTC)

Thank you. Edit request made. Warudo (talk) 18:37, 15 May 2026 (UTC)

And  Done. --Redrose64 🌹 (talk) 20:37, 15 May 2026 (UTC)

I can confirm this fixed the issue! Warudo (talk) 20:48, 15 May 2026 (UTC)

I think just the one line needed to be reverted, rather than the entire edit. (I don't have enough familiarity with the wide variety of infoboxes to do adequate testing, so I didn't investigate further.) isaacl (talk) 21:32, 15 May 2026 (UTC)

They're userboxes, not infoboxes. --Redrose64 🌹 (talk) 22:16, 15 May 2026 (UTC)

I apologize for accidentally typing the wrong word. isaacl (talk) 23:21, 15 May 2026 (UTC)

I made Template:Userbox/sandbox/styles.css and readded those lines to it (and changed Module:Userbox/sandbox to use it). I can't see any difference between {{userbox}} and {{userbox/sandbox}} in Template:Userbox/testcases. Did removing these lines actually cause an issue? Warudo (talk) 22:26, 15 May 2026 (UTC)

If the CSS class names aren't different between the sandbox and the live version of a TemplateStyles page, then the results cannot be compared on a /testcases page, because the page will be getting the effects of both /styles.css and /sandbox/styles.css. A couple of months ago I really wanted to compare CSS for Template:Signpost/Crossword on its /testcases, so I resorted to adding -sandbox to each CSS class name: Special:Diff/1339655092/1355444423. —⁠andrybak (talk) 22:09, 21 May 2026 (UTC)

You can look at Template:Reflist/testcases for a way to work around that. Anomie⚔ 22:24, 21 May 2026 (UTC)

Template {{Test case nowiki}} helps avoiding duplication, but using it with multi-part templates can be tricky. Luckily, the new CSS names can be wrangled the same way that subtemplates are handled – via {{Replace|__TEMPLATENAME__|...}}: Special:Diff/1339021964/1355452882. —⁠andrybak (talk) 23:24, 21 May 2026 (UTC)

Thanks to the above editors for taking care of this issue while I was on a long wikibreak. I made that initial edit to resolve the Linter's complaints about dark mode not having a text color specified when a background color was specified, so with a full revert, those complaints might reappear on some pages that use this CSS style sheet. YMMV. – Jonesey95 (talk) 00:36, 24 May 2026 (UTC)

I am posting this for awareness. Yahoo are blocking all incoming emails from Wikimedia. This means that if you have assigned a Yahoo email address to your Wikipedia account settings you won't receive any emails originating from @wikimedia.org. This includes emails from other editors, email alerts and, most importantly, verification codes for logging in if you haven't set-up WP:2FA.

A bug report has been opened on Phabricator but, as the issue is on Yahoo's side, we have wait for them to remove the block. Obi2canibe (talk) 16:36, 15 May 2026 (UTC)

I've been trying to log in for days. I did get a code 4 days ago, but with a delay of a few days - pretty useless. Until this is fixed, can you, please, stop asking for the log-in code @Obi2canibe ~2026-29262-94 (talk) 17:22, 15 May 2026 (UTC)

And just like that, I received two codes after waiting for some 40 minutes, neither of which worked. It says they will expire in 1 day, but with every attempt to log in they will send you another code. ~2026-29378-51 (talk) 17:44, 15 May 2026 (UTC)

Good thing I saw this, since I had used a Yahoo email. Time to change that after 15 years... - The Bushranger _{One ping only} 02:15, 16 May 2026 (UTC)

The phab: ticket has been closed as "resolved". --Redrose64 🌹 (talk) 14:11, 20 May 2026 (UTC)

When the title of a case in Category:Lists of United States Supreme Court opinions by term spans more than three vertical lines of text, some extraneous whitespace appears below the color-coded cells. This is confusing because it visually suggests two cases appear under the same title and in the same row.

On my wide monitor, several rows in 2022 term opinions of the Supreme Court of the United States are affected, such as row 17's Financial Oversight case. I took a look at Module:SCOTUS-termlist-entry and {{SCOTUS-termlist-start}}, where it is not immediately obvious to me where the problem is. I suspect it has to deal with hardcoding height as 3.7 em in some places within the module, but I don't know. Can someone with more experience take a look and, if it's not just me, implement the appropriate fix? Urve (talk) 17:56, 15 May 2026 (UTC)

Yes, I agree with your suspicion that setting the height to 3.7em is the issue. Changing things to height: 100% doesn't appear to fix the problem.

Probably not coincidentally, having internal tables is not very accessible also. Changing these to flex divs with some flavor of height: 100% would probably fix both issues. Izno (talk) 18:10, 15 May 2026 (UTC)

I've made a change here along the lines of what I suggested, but can't correct the issue reported. I might have decreased its prevalence with some of the CSS changes. It might still be possible if we make a bunch of grids of each cell and then hack in the appropriate spacing for each subopinion. Izno (talk) 22:30, 17 May 2026 (UTC)

Thank you! I have been watching your changes with some interest ;), and think they're a big improvement. Urve (talk) 19:18, 20 May 2026 (UTC)

I require assistance in mass-editing cca. 150 pages with the following configuration. Add before and after year links in navboxes not containing before and after year links for years: Template:1877 in tennis -> Template:2013 in tennis with the regex replacement provided in the link. 8rz (talk) 14:49, 16 May 2026 (UTC)

You want links similar to 2024 and 2026 in Template:2025 in tennis. They go to Template:2024 in tennis and Template:2026 in tennis. We don't usually link templates in mainspace except "V T E" links for a displayed template. The title link of the navbox is the article 2025 in tennis. Shouldn't "2024" and "2026" around it link to the articles 2024 in tennis and 2026 in tennis? If we make the links with a new template then the targets and styling can be in one place instead of having to edit every template again if we want to change something. PrimeHunter (talk) 15:08, 16 May 2026 (UTC)

Fair point, but that would require editing all of the navs to add the new template. I would create one myself but don't know how to set it up so it only detects the year in a page title and then use #expr:year+/-1 for the links in the |title param. 8rz (talk) 15:17, 16 May 2026 (UTC)

{{Title year}} could get the year but a transcluded template cannot retrieve its own page name. It's dangerous to rely on every article having the right year in the title so I would pass the year as a parameter, e.g. with |{{subst:title year}} saved in the templates. PrimeHunter (talk) 15:33, 16 May 2026 (UTC)

saved in the templates The new template or only the navs that would be using the new template or both? 8rz (talk) 15:39, 16 May 2026 (UTC)

Only the navs that would be using the new template. PrimeHunter (talk) 17:13, 16 May 2026 (UTC)

Started a new template: Draft:Template:Nav year links. Am trying to add the parameter. Some assist would be beneficial. 8rz (talk) 18:32, 16 May 2026 (UTC)

I have discovered that the code for the 2024 link in Template:2025 in tennis says [[{{NAMESPACE}}:2024 in tennis|2024]]. That means it already goes to the article 2024 in tennis as I wanted when the template is used in 2025 in tennis. It's only on the template page it links another template. The system breaks in all other namespaces than main and template, e.g. giving the red "2023" link to Draft:2023 in tennis in Draft:2024 Matthew Ebden tennis season#External links. It's not a big problem but a general nav template without such issues would still be nice. PrimeHunter (talk) 20:36, 16 May 2026 (UTC)

@PrimeHunter, having created the basic template that adds before and after years

{{align|left| « [[{{title year -1}} in tennis|{{title year -1}}]]}} {{BASEPAGENAME}} {{align|right| [[{{title year +1}} in tennis|{{title year +1}}]] » }}, although this:

{{align|left| « [[{{#expr:{{title year}}-1}} in tennis|{{#expr:{{title year}}-1}}]]}} {{BASEPAGENAME}} {{align|right| [[{{#expr:{{title year}}+1}} in tennis|{{#expr:{{title year}}+1}}]] » }} works as well.

How would you add the title year param? I've been trying every which way I could think of, but still nothing. Would it be something along the lines of {{#if:{{{toc year}}}|toc year|}}? Or a simple {{{toc year}}} would do? What do you think? 8rz (talk) 11:34, 20 May 2026 (UTC)

I have an idea for a new option for the "suggested articles" feature, which gives the linking stuff, copyediting, etc. Could we make an "anti-linking" feature, where if a link shows up twice in the same section, it could be removed?

This would be like the suggestion feature on gadgets, but could be exclusively searched for. Wikipedian12512(alt) (talk) 21:02, 18 May 2026 (UTC)

Please confirm if I understand correctly: I believe you are proposing that the Suggestion Mode feature which highlights existing duplicateLinks within a paragraph, should be extended into an equivalent feature within the Newcomer Homepage, so that you (and others) can fix these issues en-masse across all articles.

If that is accurate: I completely understand the desire to improve many articles, but I'd also highlight that part of the goal of the Suggestion Mode feature is to provide complete-newcomers with relatively easy and non-controversial edits that they could make, to help gently onboard them to the editing process (and also to encourage them to look at specifically-relevant guidance/documentation whilst they're doing so, to gently onboard them into the hundreds of existing documentation pages!). Therefore I believe this particular type within Suggestion Mode isn't ideal for the Newcomer Homepage modules, as we generally want to leave some of the easy ones around for those newcomers. For comparison, this is similar to the way that opensource code projects often have a listing of phab:tag/good-first-tasks which would be relatively easy for an experienced-developer to resolve, and are purposefully left available for helping to onboard newcomers.

Let me know if that is an accurate description of your proposal, and if it's an understandable/agreeable response! I appreciate the idea and enthusiasm, either way. Quiddity (WMF) (talk) 21:55, 18 May 2026 (UTC)

That is indeed my idea. If necessary, we could make a cap of using that feature to exclusively search for articles, so someone could only use it, say, 5-10 times a day. Thanks for the feedback! Wikipedian12512(alt) (talk) 11:50, 19 May 2026 (UTC)

Note the technical Village Pump is for questions related to technical aspects of the current Wikipedia installation, so discussion of new ideas may not reach the desired interested audience here. It may be better to discuss ideas related to newcomer features at the Talk:Growth page at mediawiki.org, or Wikipedia talk:Growth Team features. isaacl (talk) 22:12, 18 May 2026 (UTC)

I wanted to propose it at the gadget area, but it said that proposals like these should be posted here. Did I misunderstand them? Wikipedian12512(alt) (talk) 11:51, 19 May 2026 (UTC)

Can you clarify to what you are referring as the "gadget area"? Can you provide a link? isaacl (talk) 15:28, 19 May 2026 (UTC)

special:preferences. Go to the beta area, which I seem to have accidentally referred to a "Gadgets," then find the suggestions area. Wikipedian12512(alt) (talk) 15:30, 19 May 2026 (UTC)

I don't see any suggestion on the preferences page that ideas for new features should be posted at the technical village pump. Naturally you might find people interested in your proposal here, as you might on a variety of discussion pages. Just letting you know that this page isn't used to establish consensus support for new features, and the related talk pages for the growth team features are the best place to find users interested in the newcomer home page. isaacl (talk) 16:48, 19 May 2026 (UTC)

The place I went to first said I should do this here. Sorry if I shouldn't. Wikipedian12512(alt) (talk) 16:57, 19 May 2026 (UTC)

I just received two emails stating that a particular editor had posted to my user talk page. In looking at their posting history, it appears that I received these email notices about 48 hours after they had posted to my user talk page. Is this a known behavior? Do we know what causes it? Robert McClenon (talk) 08:03, 19 May 2026 (UTC)

Some info is at Wikipedia:Village pump (WMF)#Hopelessly locked out, need help. Also see #Yahoo blocking Wikimedia emails above if using Yahoo email. Johnuniq (talk) 08:31, 19 May 2026 (UTC)

My email provider sold or transferred their email service to aol.com, and aol.com and yahoo.com are two names for the same service. So it apparently was not a Wikipedia thing but a Yahoo thing. Ugh. Robert McClenon (talk) 05:59, 20 May 2026 (UTC)

Every time someone edits List of largest exoplanets I get a notification that "A link was made from List of largest exoplanets to Catastrophically evaporating planet" even though no such link was made. Why is this happening and how can it be stopped without muting link notifications? Fdfexoex (talk) 20:28, 19 May 2026 (UTC)

If the initial page is included in a template, then you get notifications every time that template gets added to a page. You can mute these notifications for individual pages at Preferences → Notifications → Muted pages for page link notifications. ClaudineChionh (she/her · talk · email · global) 22:11, 19 May 2026 (UTC)

@Fdfexoex: The link is in the last template {{Exoplanet}} at the bottom. I don't think you get a notification every time but the page is hovering around the post-expand include size limit, currently using 99.92% of the allowed. If an edit breaks the limit then the navbox with the link isn't transcluded. If the next edit is within the limit then the navbox adds the link again and you get a notification about a link which wasn't present in the rendering of the previous revision. The diff doesn't reveal this so I can understand your confusion. PrimeHunter (talk) 22:27, 19 May 2026 (UTC)

Ok, thanks for the explanation. Fdfexoex (talk) 22:37, 19 May 2026 (UTC)

Hi everyone,

In February we shared that the Reader Growth team had started work on rolling out an Image Browsing feature to make it easier for mobile web readers to discover images in Wikipedia articles, building off an earlier conversation from November of last year. Following promising experiments and various discussions with volunteers on wiki and in Discord, we plan to make this feature available in beta for all wikis the week of May 25.

We see from surveys of global internet users that a top request from readers is “more images/photos” on Wikipedia. In light of trends showing that fewer people, especially among younger generations, are coming to Wikipedia, we want to better highlight the wealth of images Wikipedia has. This Image Browsing feature adds a horizontal image carousel on mobile (the Minerva skin) showing thumbnails of an article’s images at the top of article pages with 3+ images. It displays all images in the article where the reader can easily see them, as shown below, in addition to continuing to display them in the sections where editors have placed them.

We saw promising results from testing Image Browsing in November 2025 (Phase 1 in our experimentation framework). In the test, we saw a high portion of readers tapping on the images (7.8 - 8.7% across wikis) and statistically significant increases in how many readers came back to the wiki after seeing the feature. More information on the experiment is available at our project page.

Because of these positive test results, and because of the conversations we have had with volunteers, we are moving forward to Phase 2 of rolling this feature out (Note: we do not move all features to Phase 2! For an example where we did not, see the “Mobile Table of Contents” row on our public list of experiments).

Upcoming: Beta Launch (Phase 2.1) and Rollout (Phase 2.2)

During and following that Phase 1 test, we received community input and added the following improvements to the feature over the past few months in response:

• Controls for editors to exclude specific images from appearing in an article’s carousel
• Controls for editors to exclude specific articles from getting the carousel at all
• A setting enabling logged-in users to turn off the image carousel for their account

We are planning a beta launch (Phase 2.1) for the week of May 25. This means that anyone who has all beta features on by default will start to see this feature, and others can check the box to turn it on in their preferences. The beta launch is a time that experienced Wikipedians can try Image Browsing out and let us know of any recommendations for making the feature more sustainable for editors, before we move to a full deployment to all logged-out readers on mobile web. It is also a time that editors can mark photos that they think should be excluded from the feature and articles that shouldn’t display the feature. If the launch in beta goes well, we will move forward with full feature rollout to all readers (Phase 2.2) once our bug fixes stabilize, as early as June 15.

After full rollout, we will continue to monitor data and user thoughts to notice whether things are going well or whether we should make changes.

We will update in this thread when the beta feature is live for you to try out. In the meantime, please let us know any thoughts you have on Image Browsing and consuming multimedia here or at the project page.

Thank you!

SherryYang-WMF (talk) 23:43, 19 May 2026 (UTC)

It seems the oldest Wikipedia skin is Vector 2010; is there any way to make Wikipedia look something like it did in the 2000s or so? Thanks for your time! Cheers, 𝔰𝔥𝔞𝔡𝔢𝔰𝔱𝔞𝔯 ^{(𝔱𝔞𝔩𝔨)} -⃝⃤ (they/he) 04:46, 20 May 2026 (UTC)

No, the oldest skin presently is Monobook, which was the skin on Wikipedia for some 6-7 years before Vector 2010. Izno (talk) 05:08, 20 May 2026 (UTC)

Ah, thank you; I didn’t know that. Cheers! 𝔰𝔥𝔞𝔡𝔢𝔰𝔱𝔞𝔯 ^{(𝔱𝔞𝔩𝔨)} -⃝⃤ (they/he) 05:42, 20 May 2026 (UTC)

@Shadestar474: See WP:SKIN#Deprecated skins: there are also Cologne Blue and Modern, both older than Vector, but more difficult to enable. --Redrose64 🌹 (talk) 13:51, 20 May 2026 (UTC)

Unfortunatly nostalgia was removed which was the true 2000s skin :( . You can still see it at https://nostalgia.wikipedia.org Bawolff (talk) 17:24, 20 May 2026 (UTC)

Is Template:Most appropriate article able to be set up so it automatically appears as an edit notice, similar to how Template:Refideas does? I looked into it myself but couldn't figure out how to make it work. If anyone could fix this, it would be greatly appreciated! Thebiguglyalien (talk) 16:58, 20 May 2026 (UTC)

Interested in the impact of content drift on failed verification of cited content? You may be interested in the discussion at WT:Verifiability#Content drift. Thanks, Mathglot (talk) 21:30, 20 May 2026 (UTC)

Recently, the image count (X out of Y) in MediaViewer disappeared. Is there any way to get it back via custom styling? JayCubby 22:33, 21 May 2026 (UTC)

It appears for me if I resize the window while viewing an image with MediaViewer, but then the count doesn't change when I cycle through the images on the page. PrimeHunter (talk) 00:15, 22 May 2026 (UTC)

@ ~2026-30735-11 (talk) 14:45, 22 May 2026 (UTC)

In Big Duck (at least until this revision), I had a {{mapframe}} with the default frame-width of 300, which looked awkward mixed in with all the image thumbnails at their default width of 250. So I fixed that by changing the frame-width to 250. The problem is, thumbnails are only 250 in the default size. If somebody has changed their thumbnail size in their user preferences, the mapframe doesn't track that. Is there a good solution for this, i.e. some way to make mapframe frame-size pick up the user's thumbnail size preference?

Do we have any statistics on how many people actually change their thumbnail size? If it turns out to be like 0.01%, it's just not worth worrying about. RoySmith (talk) 15:00, 22 May 2026 (UTC)

It is likely that the mapframe template in its code (the lua part) is assigning the "thumb" class to the image which thus pulls in the user preference for thumbname size. It feels like there should be a way to override this via the template call for cases like this Masem (t) 15:46, 22 May 2026 (UTC)

Somewhere on phabricator an engineer said most people do not set their thumbnail sizes and out of those that do most are using 180px. 180px is the most common option because users where set to that when the default size stopped being 180px. Snævar (talk) 16:46, 22 May 2026 (UTC)

I thought I had a larger than default thumbnail size, set in a specific number of pixels, but when I went to my preferences to check I saw that the only choices for thumbnail size were "small", "regular", and "large", and that mine were set to regular. Also the caption for this preference item says that "Standard size is 250 pixels" but "standard" is not one of the options. Is this a recent change to the UI?

Anyway, I have restored my image preference to "large", because "regular" (250px) was too small, but "large" (500px) is too large. I want something in between. Is there no longer any way of achieving that? —David Eppstein (talk) 18:23, 22 May 2026 (UTC)

T424909 RoySmith (talk) 18:31, 22 May 2026 (UTC)

At time of writing: Small is 180px. Regular/standard is 250px. Large is 400px.

Can you use CSS to adapt the size of the map based on the preference? The preference will add html.skin-thumbsize-clientpref-large or html.skin-thumbsize-clientpref-small for non-standard thumbnail choices. All of these classes can be used inside mw:Extension:TemplateStyles

In general I think it's not a good idea to avoid using fixed width/height attributes to ensure these adapt well for mobile. Jdlrobson (talk) 23:42, 22 May 2026 (UTC)

I agree with you in general about not embedding fixed widths. But at the same time, things like the mapping extension need to expose some reasonable way to make that possible without generating ugly output. Thank you for pointing me to Extension:TemplateStyles, but reading the docs, that just seems way too complicated. So I guess I'll just live what what I've got now. RoySmith (talk) 00:03, 23 May 2026 (UTC)

@Snævar I think this might be phab:T211661 - in 2022, 98.9% of users had the default (220px), though because of fixed size images on wikis etc it was only about 11% of all file requests. Andrew Gray (talk) 11:34, 24 May 2026 (UTC)

Thanks, there are so many bugs on this that it has become mush in my brain. In that bug Ladsgroup said:

"In other words, 98.9% of users are using the default and the second most popular one is 0.33%."

That comment also says: '"2" being the default' and the values are "[ 120, 150, 180, 200, 220, 250, 300, 400 ]" mw:Manual:$wgThumbLimits says the list starts at 0, so 2 is 180. Snævar (talk) 12:11, 24 May 2026 (UTC)

@Snævar Huh, interesting. There's an earlier "for most users, it goes to 220px. That's the default thumbsize" so it seems that comment has both answers!

For what it's worth, phab:T355914 (2024) had 220px as the default with a request to up it to 250px. Andrew Gray (talk) 22:53, 24 May 2026 (UTC)

When previewing an edit the default parameters of {{multiple images}} don't appeat to be having any effect. The issue goes away once the edit is saved. Discussion on the templates talk page. -- LCU ActivelyDisinterested «@» °∆t° 16:10, 22 May 2026 (UTC)

The issue appears to effect other objects. Take for instance Administrative divisions of Krasnoyarsk Krai#Administrative and municipal divisions, if you edit and preview the section the map aligns left even though it's using |frame-align=right. Outside of editing the map correctly aligns to the right hand side. -- LCU ActivelyDisinterested «@» °∆t° 19:10, 22 May 2026 (UTC)

I would guess this was broken by phab:T424687. Izno (talk) 19:18, 22 May 2026 (UTC)

Looks like Module:Mapframe and Module:Multiple image are effected then, could well be more. -- LCU ActivelyDisinterested «@» °∆t° 19:25, 22 May 2026 (UTC)

It doesn't seem that anyone at phab is interested, this is still broken. -- LCU ActivelyDisinterested «@» °∆t° 11:44, 24 May 2026 (UTC)

Sammy Byrd (edit | talk | history | protect | delete | links | watch | logs | views)

Something odd is happening on this article. File:SammyByrdGoudeycard.jpg appears in the article body and in an infobox. But, its syntax is in the body and not included in the infobox. – Muboshgu (talk) 18:28, 22 May 2026 (UTC)

I edit conflicted. Originally posted under this title. "Image appearing in infobox that isn't in the wikitext" 1brianm7 (talk) 18:30, 22 May 2026 (UTC)

In the article Sammy Byrd, a professional baseball player and golfer, there are two images in the infobox. One is an image of Byrd called in the infobox working as usual. The other is a baseball card already present in the article that, confusingly, is put in the golf career section and not called in the wikitext. I assume that it is some combination of the infobox being made from infobox person calling both infobox baseball biography and infobox golfer, and the card being present in the associated Wikidata entry, but I have no clue how to fix it. Whatever I do in the edit window, the baseball card still appears. I have checked this and it appears logged-in Vector 2010 on Google Chrome, logged-out on Vector 2022 on Internet Edge, and on the mobile app. 1brianm7 (talk) 18:29, 22 May 2026 (UTC)

@Muboshgu and 1brianm7: {{Infobox golfer}} has pulled a default image from Wikidata since this edit way back in August 2016. As originally coded, it would only do so if the |image= parameter was entirely absent. This meant that using a blank |image= parameter would suppress the Wikidata image. But since this edit in December 2025, that no longer occurs: whether |image= is present or not, if no value for it is set, the Wikidata image is always displayed. In the case of Sammy Byrd, the image concerned was added to Wikidata with this edit in August 2015. --Redrose64 🌹 (talk) 20:37, 22 May 2026 (UTC)

Can someone with more knowledge than I look at Results of the 1999 New South Wales Legislative Assembly election? Whole ton of Node-count limit exceeded errors displaying on the page, which has also landed it in WP:DUPARGS, but I'm not seeing any recent changes that could have in any way caused this error (which by my eye, popped up in the last 24 hours). Anyone know wtf is going on here? Zackmann (^{Talk to me}/_{What I been doing}) 06:33, 23 May 2026 (UTC)

@Zackmann08: It breaks Help:Template limits#Preprocessor node count. This can happen when a used template is edited. It's the only article in Category:Pages where node count is exceeded so it's not a general problem with a template. PrimeHunter (talk) 12:18, 23 May 2026 (UTC)

User:Zackmann08 recently had to fix an error I inadvertently caused by simply adding a figure in metres to elevation parameter in the infobox for a municipality in Honduras. Can somebody use an automated tool to fix the infobox parameters in the other municipality articles for Honduras from |elevation= to |elevation_m= . An example here. To avoid other editors causing the same issue again. ♦ Dr. Blofeld 07:26, 23 May 2026 (UTC)

@Dr. Blofeld: I suggest that you make a request at WP:AWBREQ. --Redrose64 🌹 (talk) 09:52, 23 May 2026 (UTC)

Will do, thanks. ♦ Dr. Blofeld 11:10, 23 May 2026 (UTC)

This is not a valid use of AWB as these parameters are nto actually in use. This is a solution without a problem. If you would preview your edits before saving them, this would not be an issue. I will also say that I monitor this category daily and have for months and this is the first time this particular issue has popped up. So again, a solution without a problem. Zackmann (^{Talk to me}/_{What I been doing}) 16:33, 23 May 2026 (UTC)

Hey folks. About {{Contentious topics/editnotice}}, how do you make it behave as an edit notice? That is, how do you get it to appear when editing an article, and not appear when merely viewing an article? Or am I confused about how it's supposed to behave? In a related question, do you have to be an administrator to make it work? The Magazine (firearms) article is where it's displaying when in view mode. — Mudwater ^(Talk) 16:30, 23 May 2026 (UTC)

@Mudwater: You need the template editor right (all admins have this, as do these users). If you have this right, go to the page concerned (let's assume Magazine (firearms) for the purposes of this explanation) and click the "Edit" tab or any "[edit]" link. Above the top-right corner of the edit box you will find a "Page notice" link, which may be red or blue. Clicking this link will open up the edit notice specific to that page, in this case Template:Editnotices/Page/Magazine (firearms). In its edit window, paste in the code, preview and save. Next time that you go to Magazine (firearms) and click an edit tab or link, the editnotice is displayed.

If you don't have the right, directions to request that an editnotice be set are at Wikipedia:Editnotice#How to request an editnotice. --Redrose64 🌹 (talk) 16:54, 23 May 2026 (UTC)

Alternatively page mover will also allow you to create editnotices. Tenshi! (Talk page) 17:02, 23 May 2026 (UTC)

Excellent. Thank you. — Mudwater ^(Talk) 18:00, 23 May 2026 (UTC)

Copy First Hundred Years’ War into the search bar and hit Enter and you'll end up at First Hundred Years' War even though no redirect exists at First Hundred Years’ War. This behaviour is similar to what happens if you try searching from a capitalisation for which no redirect exists (eg. FiRst HunDred YeArs' wAr doesn't exist, but FiRst HunDred YeArs' wAr will still take you to the article).

However, strangely, the same isn't true for The Cat’s Meow (The Cat’s Meow). Copy/pasting that and hitting Enter sends me to the search results not to The Cat's Meow. Why does the search bar handle these examples differently? Is this intentional? – Scyrme (talk) 08:54, 24 May 2026 (UTC)

@Scyrme: I guess it's because there are two matches with different targets if you also allow a capitalization change: The Cat's Meow and The cat's meow. The latter redirects to Cat's meow. Cat’s Meow only has one matching target and goes directly there. PrimeHunter (talk) 10:09, 24 May 2026 (UTC)

Varying the capitalisation without curly apostrophe, it defaults to The cat's meow regardless of how you vary it (eg. The CaT's MeOw) unless you match the case in The Cat's Meow exactly. Strange that it wouldn't do the same when substituting the apostrophe. Was this a deliberate choice or is this due to a technical limitation?

The main reason I'm asking is because Pppery added the curly apostrophe to the title blacklist to ensure that article titles aren't accidentally created at such titles (since MOS:CURLY discourages curly quotes/apostrophes, and article titles need to be linkable in article text). However, this blacklist also prevent creating redirects with a curly apostrophe. This would usually be fine, since if someone copypasted a title with a curly apostrophe into the search bar they'd still end up directly at the article without a redirect, but with The Cat's Meow this doesn't happen. – Scyrme (talk) 10:54, 24 May 2026 (UTC)