Wikipedia:Village pump (technical)

 Policy Technical Proposals Idea lab WMF Miscellaneous 

• Table of contents
• First discussion
• Jump to bottom
• New topic
• All village pumps

The technical section of the village pump is used to discuss technical issues about Wikipedia. Bug reports and feature requests should be made in Phabricator (see how to report a bug). Bugs with security implications should be reported differently (see how to report security bugs).

If you want to report a JavaScript error, please follow this how-to page. Questions about MediaWiki in general should be posted at the MediaWiki support desk. Discussions are automatically archived after remaining inactive for 5 days.

« Archives, 210, 211, 212, 213, 214, 215, 216, 217, 218, 219, 220, 221, 222, 223, 224, 225, 226, 227, 228, 229, 230

The multiref2 refs at the 0 article are giving me grief

I was correcting various cites at this article but 9 Harv warnings remain because of multiref2 issues:

• Ref #1: 2 Harv warnings
• Ref #2: 2 Harv warnings
• Ref #63: 2 Harv warnings
• Ref #70: 3 Harv warnings

I am stumped as to how to get all those multiref2 cites to work correctly. Article still in Category:Harv and Sfn no-target errors because of the 9 remaining Harv warning-issues in the multiref2 cites: #1, #2, #63, & #70. I also posted about this at Wikipedia talk:WikiProject Mathematics. If someone here could fix these refs, that would be great because I just can't see what's wrong. Thanks. - Shearonink (talk) 17:19, 11 June 2026 (UTC)

Article still in Category:Harv and Sfn no-target errors... Umm, no it's not. Harv warning: ... messages created by script do not add articles to the category.

If you wish to suppress the Harv warning: ... messages, adding |ref=none to the offending citation templates should be all that needs doing.

—Trappist the monk (talk) 17:52, 11 June 2026 (UTC)

Ok, my mistake re:the warnings. But those refs aren't really ref=nones, they are being used. So why am I getting these invalid Harv warnings? Thanks - Shearonink (talk) 18:30, 11 June 2026 (UTC)

Sure, they are used, but there are no short-form templates ({{sfn}}, etc) linking to them. When there are no short-form templates linking to a long-form template, the script emits that message. The script neither knows nor cares about {{multiref2}}. The primary purpose of that warning message is to notify concerned editors that the short-to-long link is missing. Most often, that means that the long-form template is in the wrong section and should be in §Further reading or should be removed altogether.

|ref=none tells Module:Citation/CS1 to suppress the creation of an anchor ID (CITEREFHarper2011, from ref 1 (permalink) for example). When a long-form template does not have an anchor ID, the script does not look for a short-form link to that long-form template so does not emit the Harv warning: ... message. Granted, |ref= is probably not the best parameter name, but it has been with us for as long as cs1|2 templates have been with us so replacing it with a better-named parameter would be a battle up a hill I don't care to die on.

—Trappist the monk (talk) 18:52, 11 June 2026 (UTC)

@Shearonink, those bundled citations are in a list. The script is ignoring <ref>full citation</ref> and checking <ref><ul><li>full citation1</li><li>full citation2</li></ul></ref> Bundling citations with any of the multiref templates, the list templates, or asterisk markup will give the second type of output. Rjjⁱⁱⁱ (talk) 03:47, 17 June 2026 (UTC)

Question

I'm not sure of the apt forum for this, but why does audio files with captions pop up full screen in mobile without the option to simply play it without captions and not have it pop up every time. Compare UK and Ukraine. One of them full-screens with the subtitles and the other has none so it does not. Can this be avoided? Using Chrome on an iPhone. ~2026-34629-56 (talk) 10:46, 12 June 2026 (UTC)

Because it has no funding and this is easier to maintain. —TheDJ (talk • contribs) 16:15, 12 June 2026 (UTC)

No funding? Really? ~2026-34629-56 (talk) 17:18, 12 June 2026 (UTC)

@~2026-34629-56 I do think it is a good default to display Closed Captions if they are available. While File:Президентський оркестр Гімн.ogg does not have subtitles, while File:United States Navy Band - God Save the Queen.oga does have subtitles.

I do not see an immediate way to disable displaying substitles on a user setting level nor on specific Wikipedia pages. The feature is described at mw:Extension:TimedMediaHandler, which has limited maintenance. I do think it is a good default to display Closed Captaions if they are available. ~ In solidarity 🦝 Shushugah (talk) 13:06, 13 June 2026 (UTC)

It's unusual that they do not let you disable captions. Strange. ~2026-34629-56 (talk) 15:57, 18 June 2026 (UTC)

Need to change email, but the address I registered with is dead

Transferred by me from the Help Desk. Nyttend (talk) 23:44, 14 June 2026 (UTC)

Hi! I've been inactive for a long time but would like to edit occasionally. My old email (NawlinWiki@cox.net) is from a provider that no longer provides email, so that address is dead. I can't change it because when I try to, the system prompts me for a 2FA link sent by email to the dead address. Is there a fix for this? Thanks, NawlinWiki (talk) 20:04, 14 June 2026 (UTC)

Hi, User:NawlinWiki, scroll up a few sections to the "HELP! Caught in a 2FA dilemma" section. Looks like there's an email address you can contact. Nyttend (talk) 23:49, 14 June 2026 (UTC)

Also note the process described at m:Help:Account recovery. -- zzuuzz ^(talk) 23:55, 14 June 2026 (UTC)

Used an authenticator app and was able to change my email! Thanks! NawlinWiki (talk) 04:13, 15 June 2026 (UTC)

Might be a moot point by now, but in case you used it for anything else, you should know that cox.net email addresses are still supported but have been transferred to Yahoo. You should still be able to access it through their website. DrOrinScrivello (talk) 19:50, 16 June 2026 (UTC)

Avoidwrap shrinks font size on mobile

Currently visible on the front page inside {{In the news}} RD, the name Ciarán Ó Lionáird is wrapped in {{avoid wrap}} which gives <span class="avoidwrap" style="display:inline-block;">. On mobile, this name appears in a smaller font size than the other names following / surrounding. (Not reproduced in desktop browser tools responsive emulation). Chowmein 🥡 (talk) 08:09, 15 June 2026 (UTC)

It looks normal to me in Safari on an iPhone and in the mobile version with Firefox on Windows 11. Does it happen at https://en.wikipedia.org/wiki/Main_Page?safemode=1? PrimeHunter (talk) 09:39, 15 June 2026 (UTC)

Sorry, I should have mentioned: desktop mode on mobile. Chowmein 🥡 (talk) 02:37, 16 June 2026 (UTC)

That also looks normal to me in Safari on an iPhone. PrimeHunter (talk) 10:15, 16 June 2026 (UTC)

Strange, that's what I used originally. I just checked on a second iPhone also using Safari and it appears small there as well. Chowmein 🥡 (talk) 19:47, 16 June 2026 (UTC)

Browsers try to be smart about what they think is important and what is not for web pages that they don't think were designed for mobile resolutions. When you use the desktop website on mobile, that is one such case.

In such cases, content they guess is important will be bigger and content they guess is not will be smaller. I would guess that setting a span to inline-block is one signal they use. Functionally, the only way to fix this is to use a more responsive skin. Izno (talk) 01:40, 18 June 2026 (UTC)

Wow, that's fascinating! I did not know Safari was that opinionated. Great to know, thank you! Chowmein 🥡 (talk) 01:18, 22 June 2026 (UTC)

See the Mozilla Developer Network (MDN) page on the text-size-adjust CSS property for an overview of how some mobile browser engines will adjust font sizes for legibility. (In short, pages are rendered on a canvas larger than the device's actual width (unless the page specifies otherwise), scaled down to fit the screen, and the font size adjustments are made for legibility.) The MDN page links to really old (thus possibly out-of-date) pages describing the behaviour for mobile Safari, Chrome, and Gecko (Firefox). (HTML pages using modern responsive designs explicitly tell the browser to use the device width and an initial scaling factor of 1, which disables the font adjustment algorithm.) You could try setting the text-size-adjust / -webkit-text-size-adjust property for specific elements in your your common.css file, but to be honest, I think that'll just lead to a lot of pain trying to fight the font adjustment algorithm, so I don't recommend it. isaacl (talk) 14:15, 18 June 2026 (UTC)

Very interesting. I wonder if long term the maintainers of Vector would be interested in disabling this behavior. Fascinating to learn it's Safari trying to be helpful. Thank you! Chowmein 🥡 (talk) 01:20, 22 June 2026 (UTC)

As I understand it, the Vector2022 skin was designed following modern responsive design principles, but it's disabled (so the old style render-on-a-larger-canvas-and-resize approach is used by the device) pending a community consensus to enable it. I suspect the design team would rather work with the community on improving the responsive design to the point where it gains community support to be enabled.

Note it's not just Safari. All small-screen browsers follow some procedure to render pages that were never designed to fit on a small screen in a way that keeps them as legible as possible. isaacl (talk) 01:38, 22 June 2026 (UTC)

Native Name Module idea

Have an idea for a new module that I'm tentatively calling Module:Infobox native name and want to get feedback before I start down this path on whether it is worthwhile.

Background

There are tons of Infoboxes that have the pair of parameters |native_name= & |native_name_lang=. These params are designed to take the name of the subject in a non-English language along with that language's IETF language tag. This in turn will display the native name wrapped in a div like this:<div class="nickname" lang="es">Sofía</div>. What this does NOT do is display to the viewer what language is being used. If you were to use {{Native name|es|Sofía}} on the other hand, you would get: "Sofía (Spanish)". Note that this also includes the html <i lang="es">Sofía</i> so the lang tag is still in the HTML.

The proposal

What I am thinking of doing is creating a module that can be called from Infoboxes and automatically format |native_name= & |native_name_lang= to use {{Native name}}. Now the obvious easier solution would be to just have the Infobox directly call {{Native name}}. The reason that we cannot do this is that for preexisting and well established Infoboxes if we were to just drop in a call to {{Native name}} it would error on tons of pages as any page where |native_name_lang= was not currently a valid IETF language tag would error like this: {{native name|BADCODE|Joe Smith}} → Error {{native name}}: an IETF language tag as parameter {{{1}}} is required (help).

Likewise if a transclusions is calling one of the Native name/Langx templates from |native_name= such as |native_name={{langx|es|Sofia}} you would would calling {{native_name|es|{{langx|es|Sofia}}}} → Spanish: Sofia (Spanish)

All of this to say that there are numerous edge cases that would need to be handled by error checking in a module. The ONLY case where this module should do anything is where:

|native_name=Plaintext name in any language

|native_name_lang=Valid IETF language tag or Language name

Setting aside for a moment the how of doing this, I'm curious if this is a worthwhile endeavor? Is there any objection to having this sort of think done? Would this be helpful or a waste of time? Please share your thoughts! Zackmann (^{Talk to me}/_{What I been doing}) 18:08, 15 June 2026 (UTC)

If this is desirable, I think it would be better to migrate infoboxes to the new format instead of leaving them inconsistent. If native_name_lang is not a valid language tag, it should throw an error, for instance. — Qwerfjkltalk 15:00, 16 June 2026 (UTC)

@Qwerfjkl: oh for sure! Pages that meet that criteria could very easily be placed in a maintenance category to be cleaned up. What I want to avoid though is implementing this new idea and suddenly having potentially thousands of pages displaying red error messages. A silent maintenance category can and will be implemented to clean up those pages though. Great point. Zackmann (^{Talk to me}/_{What I been doing}) 16:05, 16 June 2026 (UTC)

Just add 'class="error"' to the error span in template:native_name, then do {{#iferror:{{native name|BADCODE|Joe Smith}}| maintainance cat | {{native name|BADCODE|Joe Smith}} }}. Snævar (talk) 18:57, 16 June 2026 (UTC)

@Snævar: I like the idea, but that will still result in pages that are currently displaying working code having the Native Name removed. Consider the following use case which would currently work: {{Infobox person| native_name = Zack| native_name_lang = }}. Under your solution, since there is no value for |native_name_lang= the |native_name=Zack value would be removed from being displayed entirely. It would end up in a maintenance category, but unless and until that value is resolved from the maintenance category, there would be a net loss of information from the page. The goal here is to add valuable information (i.e. what the native name's language is) but not to remove native names which do not currently have a language properly listed as this is still valuable information. --Zackmann (^{Talk to me}/_{What I been doing}) 19:10, 16 June 2026 (UTC)

@Snævar: A real word example of this would be M. Kumarasamy College of Engineering where the native name would be blanked without proper error checking. Again, I love your idea, I just think any implementation of this idea needs to be a bit more robust to account for the edge cases. Zackmann (^{Talk to me}/_{What I been doing}) 00:30, 17 June 2026 (UTC)

@Gonnym, Jonesey95, Jevansen, and WOSlinker: you all helped with my last attempt at a module (Module:Person date). Would love to hear any thoughts you have on this before I start down the road.... Zackmann (^{Talk to me}/_{What I been doing}) 00:31, 17 June 2026 (UTC)

Jujst wondering if you might just want to add to the existing Module:Native name as a separate function rather than creating a new module? -- WOSlinker (talk) 07:00, 17 June 2026 (UTC)

That is a fair point... Will likely do that! Zackmann (^{Talk to me}/_{What I been doing}) 15:56, 17 June 2026 (UTC)

I have mocked it up and requested a code review at Template talk:Native name § Code review request. Any input greatly appreciated! Zackmann (^{Talk to me}/_{What I been doing}) 19:30, 17 June 2026 (UTC)

Red dots

What are these red dots seen on source editor in this article section? I didn't add the text containing the dots and I cannot delete the dots. TurboSuperA+_[talk] 18:10, 16 June 2026 (UTC)

@TurboSuperA+ what browser are you using? Where the red dots are unicode characters that aren't the basic U+20 space character but are U+200B (zero width space) or U+20260 (word joiner), so I'm guessing your browser is highlighting these to you. Nthep (talk) 18:51, 16 June 2026 (UTC)

Double backspace erased it (when a single wouldn't). I've never seen it before. I wanted to make sure I know what it was before I break something. Thank you! TurboSuperA+_[talk] 18:57, 16 June 2026 (UTC)

You have CodeMirror syntax highlighting enabled, which by default highlights special characters. You can hover over the character itself and it will tell what it is. In this case it was a zero-width space. I don't know why you weren't able to delete it with a single ← Backspace, however. — MusikAnimal ^talk 02:16, 17 June 2026 (UTC)

You're right. I didn't think of the dot as a highlight, but it makes sense, like those reverse Ps and dots in word processors. TurboSuperA+_[talk] 05:41, 17 June 2026 (UTC)

Those reverse Ps are called pilcrows. A Wondrous Raven (talk) 00:58, 19 June 2026 (UTC) ¶

PDF won't format?

I can't figure this out, I can't get the PDF to format correctly in this article: Western African Ebola epidemic#Containment and control. Can someone help? Victor Grigas (talk) 12:18, 17 June 2026 (UTC)

Fixed with action=purge. It re-renders the thumbnail. Snævar (talk) 13:19, 17 June 2026 (UTC)

Thanks! Victor Grigas (talk) 16:52, 17 June 2026 (UTC)

Upcoming migration to Parsoid

Hello everyone, I'm following up on the April announcement about the Parsoid migration as a heads-up about the completion of this work ahead of next week.

Parsoid has been the default parser on the English Wikipedia mobile web for the past month, serving nearly two-thirds of traffic, and many users have opted in since the April announcement. That, combined with our confidence framework, makes us confident that Parsoid is ready for the next phase for English Wikipedia and will be generally available soon.

Before we complete the transition to Parsoid for desktop, we encourage you to opt in, if you haven't already, and test your workflows to raise your concerns or issues you might have found that haven't surfaced in our tests and previous user feedback. To report bugs and issues, please look at our known issues documentation, and if you found a new bug, please report it through the "Report Visual Bug" link in the right sidebar, or create a Phabricator ticket and tag the Content Transform Team in Phabricator.

The documented known issues were considered non-blockers to the rollout due to their severity or impact and are being prioritized by our team for resolution as soon as possible once rollouts are complete.

There are also known differences between Parsoid and the legacy parser, and we have compiled instructions to help editors navigate these changes. MSantos (WMF) (talk) 09:29, 18 June 2026 (UTC)

I think PageAssessments which is primarily used on enwiki, isn't compatible with Parsoid. You might want to have that fixed first. – SD0001 (talk) 16:07, 18 June 2026 (UTC)

I find it strange that phab:T221028 is not even mentioned in the known issues list or in the instructions page even though it's a change that breaks the links to many pages (like /) outside the main namespace. To me, such an issue should be enough to delay the migration until it is fixed but I guess we move fast and break things in these parts. Warudo (talk) 10:38, 19 June 2026 (UTC)

I was confused by your "outside the main namespace". Apparently what this breaks is links to mainspace articles like //Khara Hais Local Municipality or /dev/zero, when the link appears in a space that allows subpages, like Wikipedia: or User talk: . —David Eppstein (talk) 19:40, 19 June 2026 (UTC)

Yes, I agree with SD0001 that extensions in use on Wikipedia need to get a review for support in Parsoid (PageAssessments may not be the only one).

Section editing transcluded things is one of the biggest pain points remaining. There are some other bad display things as well, like how on mobile captions are display flex. There are existing tasks for these. English Wikipedia could use a round or two of visual delta testing for the N most-popular pages.

As I think I have said elsewhere, please make a dedicated location for English Wikipedia feedback when this goes live. We tend to be very noisy and I don't want VPT being swamped with all the potential issues.... Izno (talk) 23:29, 19 June 2026 (UTC)

Category changes in watchlist

How do I stop seeing Category removal/copying/addition in my watchlist? I have Category changes unchecked in my Type of change filter. Am I misunderstanding? Masato.harada (talk) 17:01, 18 June 2026 (UTC)

@Masato.harada: Are you watching the category page or the categorized pages? The setting only applies to the former. If you watch an article then there is no way to hide edits which only change the categories. PrimeHunter (talk) 17:12, 18 June 2026 (UTC)

Ah, that explains it. Thanks. Masato.harada (talk) 17:15, 18 June 2026 (UTC)

New Codex icons

Sorry if I place this here, but I've just noticed this a few minutes ago; all the icons have been updated. They are making Wikipedia new again. Any thoughts? – SimpleObjects-9ei 🏖️/☀️/🥵 (🌎 CentralAuth) 19:01, 18 June 2026 (UTC)

This is phab:T399175, which has received quite a lot of negative reviews. – SD0001 (talk) 19:23, 18 June 2026 (UTC)

As that comment-thread is long, I'll highlight the comment at phab:T399175#12035047 which gives a summary of how the constructive/precise feedback is welcome, and that there will soon be more iterations to many of the icons based on everyone's feedback. There's another task at phab:T427868 ("Icon refinement follow ups") collecting those quick follow up changes. HTH. Quiddity (WMF) (talk) 20:01, 18 June 2026 (UTC)

As someone who agrees with the many users who have expressed disappointment at the phab discussion, I'm especially interested in whether there could be a way for editors to opt-out of the recent changes (going back to what it was yesterday, in other words), until further improvements are made. I saw at the phab discussion that someone has created this: , , which didn't work for me. If there could just be an opt-in/opt-out button added to user preferences (either Appearance or Gadgets), that would be very helpful. --Tryptofish (talk) 21:26, 18 June 2026 (UTC)

I doubt they would commit to having two different versions of the icons for eternity, which is what you'd need for a preference. However someone has created User:Pattersonuwu/OldIcons.css which can be installed as a workaround. One way to install it would be to add this to your common.js file: importStylesheet('User:Pattersonuwu/OldIcons.css');. There might also be a way to @import it into your common.css file, but I haven't tested that. –Novem Linguae (talk) 00:37, 19 June 2026 (UTC)

Heyo, the documentation at User:Pattersonuwu/OldIcons shows how to add this to your common.css :3 pattersonuwu ^njz (talk) 14:22, 19 June 2026 (UTC)

Thanks, both of you. That's what I linked to in my comment. Doing it with the common.js file worked for me, and I'm happy now. --Tryptofish (talk) 20:58, 19 June 2026 (UTC)

I would recommend the common.css method since it should prevent a brief visual flash of the new icons. But anyway, glad this was helpful :) –Novem Linguae (talk) 08:02, 20 June 2026 (UTC)

I tried that just now, and the css approach doesn't work for me. I switched back to the js approach, and while I do notice that brief flash, it doesn't bother me particularly. I don't know why putting it in css has no effect for me, while js does (current version of Firefox, Legacy Vector skin), but I'm satisfied. --Tryptofish (talk) 19:52, 20 June 2026 (UTC)

@Tryptofish: You added the @import rule after the existing rules, this will not work: any @import rules must be first in the stylesheet (only blank lines and comments are allowed beforehand). See CSS Cascading and Inheritance Level 3 section 2 Importing Style Sheets. --Redrose64 🌹 (talk) 22:21, 20 June 2026 (UTC)

Thanks so much for explaining that. I simply used the "copy" button in the documentation to copy what I then pasted into my css file, so that should be corrected. It looked a bit "off" to me at the time. Maybe I'll try it again if the brief flash at the beginning starts to annoy me. --Tryptofish (talk) 23:38, 20 June 2026 (UTC)

done --Redrose64 🌹 (talk) 00:13, 21 June 2026 (UTC)

Works, thanks. --Tryptofish (talk) 17:53, 21 June 2026 (UTC)

Does anyone know why the URLs are base64 encoded? TurboSuperA+_[talk] 05:33, 20 June 2026 (UTC)

They're data URLs, so the actual image data is contained within them, rather than pointing to a location on the web. There are pros and cons to this approach. isaacl (talk) 05:51, 20 June 2026 (UTC)

That's what I thought, but why are they wrapped in url() ? TurboSuperA+_[talk] 05:54, 20 June 2026 (UTC)

That's the syntax in CSS. isaacl (talk) 07:10, 20 June 2026 (UTC)

Thanks. I actually didn't know that was possible. Very cool and useful (for some use cases). TurboSuperA+_[talk] 07:15, 20 June 2026 (UTC)

The new "DownTriangle" is terrible; it's so small now on my watchlist that's it's barely even visible. Some1 (talk) 23:09, 18 June 2026 (UTC)

Yes, everything looks to me like it was drawn, crudely, with a very thick-tip magic marker. --Tryptofish (talk) 23:13, 18 June 2026 (UTC)

Yeah, DownTriangle now looks like some Windows Vista/7/8/8.1 (RT) & Windows Server 2012/2012 R2 shenanigans (the dropdown button which you would see on the bottom right of the desktop). It looks EXACTLY like that, just that the Wikipedia version is black. I do not use Watchlist, but why they would resize downTriangle like x0.5 times tinier? And, even better, who asked for this? There shall be justice if any user is upset with the new icon update. – SimpleObjects-9ei 🏖️/☀️/🥵 (🌎 CentralAuth) 23:33, 18 June 2026 (UTC)

This sounds like phab:T429642, which is a bug and has a patch written that will be merged and deployed shortly. –Novem Linguae (talk) 00:38, 19 June 2026 (UTC)

Also, just occasionally to let you guys know, the release notes for MedaWiki 1.47/wmf.7 (first deployed 16 June 2026) shows the following line which I'll show below:

git #4c4f84d9 - Update Codex from v2.5.1 to v2.6.0 (T328496) (T361508) (T399175) (T404328) (T426193) by Roan Kattouw

The git commit must say anything about what we got for Thursday. Also, Codex actually had versions (see MediaWiki 1.38/wmf.23's release notes for a prototype version v0.1.0-alpha.3 of Codex from 2022, as an example) Just make sure to check out the rest of the Phabricator links to see what else is going on this mayhem. The one who is doing the changes is User:Roan Kattouw (WMF). He is a Wikimedia Foundation employee, so should we head over to Wikipedia:Village pump (WMF) to continue this chit-chat or what? – SimpleObjects-9ei 🏖️/☀️/🥵 (🌎 CentralAuth) 15:14, 20 June 2026 (UTC)

The person you mentioned is just the deployer. Someone else is the one redrawing the icons. More info in this ticket.

They do seem to be responding to our feedback and willing to adjust the icons that we don't like. So we may not want to make too big of a stink about this. Front end changes will always be more controversial and subjective than back end changes. –Novem Linguae (talk) 14:44, 21 June 2026 (UTC)

Just restating this here for anyone finding this thread, you can (mostly) revert this change yourself with User:Pattersonuwu/OldIcons. pattersonuwu ^njz (talk) 14:25, 19 June 2026 (UTC)

What's the performance impact of loading an 418kb css file? Sjoerd de Bruin (talk) 14:42, 19 June 2026 (UTC)

I dunno, but we shouldn't be having this conversation here anyways pattersonuwu ^njz (talk) 14:49, 19 June 2026 (UTC)

Izno, I don't see how you can deny that this (and the other two below) are ITSTHURSDAY issues. They all appeared with the latest MediaWiki revision. I have a fourth issue to report. For many years now, on category pages, the entries under the "Subcategories" heading (if one exists) are preceded by a little triangle, which normally points right, but points down when a parent cat is expanded to show its children. As of the new MediaWiki, this triangle has got much smaller, and is now too small to distinguish the right-pointing triangle from the down-pointing one. I'm not going to moan and wait while phab tickets are ignored, I'll do something about it. This CSS rule will restore the previous size:

/* restore triangles in category pages to previous size */
@supports (-webkit-mask-image:none) or (mask-image:none) {
  .CategoryTreeToggle,
  .CategoryTreeEmptyBullet {
    -webkit-mask-image: url("data:image/svg+xml;utf8,<svg xmlns=\"http://www.w3.org/2000/svg\" width=\"20\" height=\"20\" viewBox=\"0 0 20 20\" fill=\"black\"><path d=\"M10 15 2 5h16z\"/></svg>");
    mask-image: url("data:image/svg+xml;utf8,<svg xmlns=\"http://www.w3.org/2000/svg\" width=\"20\" height=\"20\" viewBox=\"0 0 20 20\" fill=\"black\"><path d=\"M10 15 2 5h16z\"/></svg>");
  }
}

It goes in meta:Special:MyPage/global.css. For those interested, and who understand SVG, the significant bit is the path M10 15 2 5h16z which overrides the path M14 7H6v2.5l4 3.5 4-3.5z used by the newest MediaWiki. --Redrose64 🌹 (talk) 20:43, 19 June 2026 (UTC)

I did not deny that it was a Thursday issue. I disagreed that it made sense to group all of these sections together strictly on the basis that they are Thursday issues. They are all more-or-less distinct issues that are coincidentally appearing at the same time and as such will have naturally different resolution paths, which we should allow to archive at the usual arbitrary rate individually.

Your icon issue seems fine to put in this section. I do think it is a mistake not to report this upstream. The issue pertaining to the watchlist reported above is already soon-to-be-resolved. Izno (talk) 21:09, 19 June 2026 (UTC)

The inbox icon has changed

Is there a place where we can read the "changelog" to find out why things were changed? I'm not opposed to change, it'd just be nice to have a heads-up/explanation. TurboSuperA+_[talk] 05:19, 20 June 2026 (UTC)

Here! Also being discussed above at #New Codex icons. Chaotic Enby (in solidarity · talk · contribs) 05:25, 20 June 2026 (UTC)

Thank you! TurboSuperA+_[talk] 05:28, 20 June 2026 (UTC)

cjkv template error

As visible in Gando Convention—an additional semicolon is erroneously added. TE(æ)A,ea. (talk) 19:12, 18 June 2026 (UTC)

Looks like it was fixed in the sandbox a few months ago, if someone wants to run through the testcases and verify before moving it over. SarekOfVulcan (talk) 19:19, 18 June 2026 (UTC)

Edit button is wonky

The "view | edit | history | purge" links on template documentation look incorrect, like [ | history ]. See Template:Template link for an example. It persists across Vector 2022, Vector legacy, and Monobook, but looks fine in Timeless. I'm guessing this is a WP:THURSDAY issue? Any help would be appreciated :) Best, HouseBlaster (talk • he/they) 20:10, 18 June 2026 (UTC)

Yes, it's a Thursday issue, and one that I am to be blamed for (at least for requesting it, I didn't do the work). Izno (talk) 20:15, 18 June 2026 (UTC)

The relevant implementation task is phab:T268900. We will need to adjust onwiki. Izno (talk) 20:17, 18 June 2026 (UTC)

Which actually doesn't have that many adjustment points, modulo whatever is happening in user space. Izno (talk) 20:27, 18 June 2026 (UTC)

Made an update to Module:Documentation that should fix the immediate impact for page-related actions for docs. (Personally I think it would look more consistent like this, too.) stjn 22:41, 18 June 2026 (UTC)

Images being massive

Resolved

I've noticed that, starting today, images using upright instead of thumb, are massive. An example of this is the images in the table on Mandurah line. The images were normal size yesterday. What's up with that? Steelkamp (talk) 08:05, 19 June 2026 (UTC)

I also see huge images in the Stations section. Certes (talk) 08:29, 19 June 2026 (UTC)

Is this part of the #"Upright" parameter in image embedding broken? problem? DMacks (talk) 08:36, 19 June 2026 (UTC)

Hmm, not sure Yesterday I was told I should convert images using px to using upright, and it was working properly then. Steelkamp (talk) 08:38, 19 June 2026 (UTC)

That timing does feel like WP:THURSDAY. CMD (talk) 09:32, 19 June 2026 (UTC)

I'm seeing the same problem with a copy of that table, plus a few more examples, at my sandbox. The upright option does not appear to be applied unless thumb is present. – Jonesey95 (talk) 14:55, 19 June 2026 (UTC)

@DMacks: It's definitely a different problem. The earlier one did not affect Firefox 152; this new problem does. --Redrose64 🌹 (talk) 17:12, 19 June 2026 (UTC)

Looks like the fix from phab:T429551phab:T424596 broke things. The parser is now outputting width: calc(@{@calc-standard}) which is invalid CSS. --Ahecht (TALK
PAGE) 15:51, 19 June 2026 (UTC)

Pinging @Jdlrobson. --Ahecht (TALK
PAGE) 15:57, 19 June 2026 (UTC)

The patch in phab:T429551 hasn't been deployed yet. From the looks of phab:T67889, "upright" has never applied to inline images unless the "frameless" format is used. ABreault (WMF) (talk) 16:00, 19 June 2026 (UTC)

@ABreault (WMF) Sorry, I meant phab:T424596, which was responsible for that invalid CSS (that's what I get for having too many tabs open at once). I think there is a stray "@" character in the patch that was rolled out, but I put more details in the task. --Ahecht (TALK
PAGE) 16:22, 19 June 2026 (UTC)

I replied on ticket. While it is true there is invalid CSS here, I am now wondering if this rule should be deleted and making this the default behaviour. We should not be making users download large megabytes images and hiding that fact by scaling them down in CSS. Jdlrobson (talk) 17:23, 19 June 2026 (UTC)

ABreault (WMF) is right. I forgot about mw:Help:Images#Rendering a single image, which says of upright, "Requires either thumb or frameless." That is not intuitive and was apparently undocumented until three years ago. Steelkamp appears to have caused these giant images in Mandurah line to render by changing px values to upright values without adding "frameless". – Jonesey95 (talk) 23:16, 19 June 2026 (UTC)

Thanks everyone for your help! Steelkamp (talk) 23:50, 19 June 2026 (UTC)

@Jonesey95: It's been documented for far longer than three years; something similar was added to WP:EIS over seventeen years ago. The earliest mention that I can find was added at 21:15, 14 June 2009 (UTC), the text at that time being "must be used along with the 'thumb' or 'thumbnail' parameter". It's been amended a few times since, such as to add frameless - which wasn't a valid option until later that year. --Redrose64 🌹 (talk) 00:04, 20 June 2026 (UTC)

Giving permanent ban to non-registered editor

While reviewing the edit history of the Wikipedia page below, I noticed that user "Singasigmaskibdiboi" added a large amount of nonsensical content and then reverted the page about a minute later: https://en.wikipedia.org/w/index.php?title=Sv%C3%A4t%C3%BD_Jur&diff=1359211049&oldid=1359210978 Could an administrator please review this behavior and consider appropriate action, including a possible indefinite block of the account (or associated IP address)? Thank you for your time and assistance.Tbartovic (talk) 17:18, 19 June 2026 (UTC)

@Tbartovic Your request would be more appropriate on WP:ANI. Izno (talk) 17:48, 19 June 2026 (UTC)

'Preview page with this template' no longer works when editing a module

Tracked in Phabricator
Task T429710
Invalid

I use that functionality a lot and now it doesn't work. I've reported this at phabricator for whatever that's worth and am posting this here as a general notification.

—Trappist the monk (talk) 22:49, 19 June 2026 (UTC)

@Trappist the monk: You changed Template:Current leader to invoke Module:Current leader/sandbox instead of Module:Current leader. Was that an accident? It means Template:Current leader/testcases uses Module:Current leader/data/sandbox instead of Module:Current leader/data. If you edit Module:Current leader/data/sandbox, enter Module:Current leader/data/sandbox in the "Template name" box and Template:Current leader/testcases in the "Page title" box, then it works as expected for me. PrimeHunter (talk) 01:50, 20 June 2026 (UTC)

Thank you. Mea culpa.

—Trappist the monk (talk) 12:56, 20 June 2026 (UTC)

Quarry help

Looking for some Quarry assistance... Trying to write a query that list every Infobox template AND the number of transclusions that each has. Doesn't seem to be working... Any help apprecaited!

SELECT 
    p.page_title AS template_name,
    COUNT(tl.tl_from) AS transclusion_count
FROM page p
LEFT JOIN templatelinks tl 
    ON p.page_id = tl.tl_target_id
WHERE p.page_namespace = 10                  
  AND p.page_title LIKE 'Infobox%'          -- Starts with "Infobox"
  AND p.page_title NOT LIKE '%/%'           -- Excludes any title containing a slash "/"
  AND p.page_is_redirect = 0                -- Exclude redirect templates
GROUP BY p.page_id, p.page_title
ORDER BY transclusion_count DESC;

Zackmann (^{Talk to me}/_{What I been doing}) 04:43, 20 June 2026 (UTC)

WP:RAQ for the future. Izno (talk) 05:08, 20 June 2026 (UTC)

Posted there and will take questions there instead in the future. Didn't know that even existed! Zackmann (^{Talk to me}/_{What I been doing}) 05:16, 20 June 2026 (UTC)

Help with a template

Please see Template talk:WikiProject Ice Hockey#Main category. AIUI it's a simple change but needs a template editor or admin. This is related to Wikipedia:Bots/Requests for approval/PhuzBot 10. WhatamIdoing (talk) 17:57, 20 June 2026 (UTC)

Skip to top and bottom covering content

{{Skip to top and bottom}} covers content in the bottom right corner on Vector 2022, as can be seen at the help desk. This is bad, as it can make text hard to read, and obstruct links. I propose either A: moving the button to the bottom left corner (demoed in the sandbox), or B: hiding it entirely in Vector 2022. I understand Matrix originally moved the buttons into the content area to stop them covering links, but that doesn't seem to happen for me. My first preference is A, but if it does cover links, then I would support B instead. Danski454 (talk) 02:58, 21 June 2026 (UTC)

An easier solution is simply removing the template. Izno (talk) 03:26, 21 June 2026 (UTC)

This matter comes up occasionally at Template talk:Skip to top and bottom, and as seen in the most recent thread there, has also come up on this page in the past. The problem is that we don't know (we cannot know) what might be behind the buttons, so we cannot position the buttons into some blank space or otherwise harmless area.

As Izno says, you can remove the template; the problem with doing that is that somebody else might restore it. Alternatively, you can hide them for yourself, leaving them visible for everybody else, as described at Template:Skip to top and bottom#Example. --Redrose64 🌹 (talk) 07:01, 21 June 2026 (UTC)

I still think that, rather than making everyone else hide it on a small random set of pages, people who want this should make a user script or gadget that would add it for themselves to every page. Or maybe even a browser extension to add it on every website. Anomie⚔ 12:23, 21 June 2026 (UTC)

I've removed the template from WP:HD (partly as a test to see if anyone objects). If we can't find somewhere harmless to put it, then I would support removing it from other pages, and marking the template deprecated. Danski454 (talk) 14:07, 21 June 2026 (UTC)

Can we please require a space after a URL in a template parameter?

I work with reference templates quite a lot, and in quick succession, and it is a minor but persistent annoyance to me that sometimes it is not easy to see exactly where a URL ends and the next parameter begins because there is no space before the next pipe. I think it would be trivially easy to have a rule that a URL in a template with parameters separated by pipes should have a space before the pipe, and have a bot go around and add those spaces. BD2412 T 03:02, 21 June 2026 (UTC)

This is not a technical question. You will want to ask this at WP:VPPRO or WT:MOS. Izno (talk) 03:27, 21 June 2026 (UTC)

@BD2412: "space before pipe" would be an excellent rule in all citation templates. DuncanHill (talk) 21:42, 21 June 2026 (UTC)

@DuncanHill and Izno: Posting this at WP:VPPR now. BD2412 T 21:48, 21 June 2026 (UTC)

Harv duplicate target error

There is a Harv error: duplicate target for CITEREFPollard2006 in History of fascism. It has to do with two chapters by the same author in a book edited by someone else. I can't see how to fix it. Can anyone help? Thanks, DuncanHill (talk) 21:40, 21 June 2026 (UTC)

Add |anchor-year=2006a or |anchor-year=2006b to the appropriate {{harvc}} templates. Change the matching {{sfnp}} templates to use those disambiguated anchor years.

—Trappist the monk (talk) 21:51, 21 June 2026 (UTC)

@Trappist the monk: Many thanks, worked straight out of the box. DuncanHill (talk) 21:56, 21 June 2026 (UTC)

Cross-wiki transclusion?

Is that even possible? Like {{meta:User:ABx11}}? --ABx11 (she/they | formerly TheAuroraBorealis | In solidarity) 22:46, 21 June 2026 (UTC)

No. User pages created at Meta do have a cross-wiki display, but transclusion of arbitrary pages or templates does not work. Izno (talk) 23:27, 21 June 2026 (UTC)

Is it normal for Wikipedia edits to take a long time to save?

I have a Dell XPS 13 9380 (2019 model) running Windows 11. My problem is that when I click "Publish changes" after making an edit, it takes like 15-20 seconds for my edits to go through. I'm not sure if this is a normal amount of time to be waiting before my changes go live. When I browse and click links, including the edit button, it loads pretty quickly. The only problem is with saving my edits. I am using source editor. My browser is Google Chrome. I have 8 GB of RAM, my CPU is an Intel Core i5-8265U, and my storage is 238 GB. My question is whether this is normal for a computer and if it is not, what I should do about it. Interstellarity (talk) 23:10, 21 June 2026 (UTC)

Save time is not a function of your computer. It is a function of the network between your computer and the WMF's computers, and a function of the WMF's computers. Izno (talk) 23:28, 21 June 2026 (UTC)

Also, when I was editing this page compared to Wikipedia talk:Vital articles/Level 4, the save time was longer on the latter page compared to this page. What's the deal with that and can it be fixed? Interstellarity (talk) 23:39, 21 June 2026 (UTC)

That page is 350k. Page size is another factor in save time. Izno (talk) 23:42, 21 June 2026 (UTC)

PDF not working

I uploaded a PDF file to Commons, File:Is Lindbergh a Nazi?.pdf, and I tried to follow the advice at Help:Extended_image_syntax#Page, but it is not working when I add it to the article Leon Milton Birkhead. I just see the file name on PC. I checked on IOS and I just see the error file that happens when I click on the page here. Everything seems to be working fine on the Commons file itself, Commons:File:Is Lindbergh a Nazi?.pdf. 1brianm7 (talk) 03:20, 22 June 2026 (UTC)