Wikipedia:Village pump (technical)#Caret color CSS change

Policy

Technical

Proposals

Idea lab

WMF

Miscellaneous

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

Shortcuts

• WP:VPTWP:VPT
• WP:VP/TWP:VP/T
• WP:TECHPUMPWP:TECHPUMP
• WP:PUMPTECHWP:PUMPTECH

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 guideline. Questions about MediaWiki in general should be posted at the MediaWiki support desk. Discussions are automatically archived after remaining inactive for 5 days.

view · edit Frequently asked questions (see also: Wikipedia:FAQ/Technical) Click "[show]" next to each point to see more details. If something looks wrong, purge the server's cache, then bypass your browser's cache. This tends to solve most issues, including improper display of images, user-preferences not loading, and old versions of pages being shown. No, we will not use JavaScript to set focus on the search box. This would interfere with usability, accessibility, keyboard navigation and standard forms. See task 3864. There is an accesskey property on it (default to accesskey="f" in English). Logged-in users can enable the "Focus the cursor in the search bar on loading the Main Page" gadget in their preferences. No, we will not add a spell-checker, or spell-checking bot. You can use a web browser such as Firefox, which has a spell checker. An offline spellcheck of all articles is run by Wikipedia:Typo Team/moss; human volunteers are needed to resolve potential typos. If you have problems making your fancy signature work, check Help:How to fix your signature. If you changed to another skin and cannot change back, use this link. Alternatively, you can press Tab until the "Save" button is highlighted, and press Enter. Using Mozilla Firefox also seems to solve the problem. If an image thumbnail is not showing, try purging its image description page. If the image is from Wikimedia Commons, you might have to purge there too. If it doesn't work, try again before doing anything else. Some ad blockers, proxies, or firewalls block URLs containing /ad/ or ending in common executable suffixes. This can cause some images or articles to not appear. For server or network status, please see Wikimedia Status. If you cannot reach Wikipedia services, see Reporting a connectivity issue.

« Archives, 205, 206, 207, 208, 209, 210, 211, 212, 213, 214, 215, 216, 217, 218, 219, 220, 221, 222, 223, 224, 225

Why is there so much additional space on Special:UserRights all of a sudden? The two columns seem to be twice the distance apart and each line is as if there's two line breaks between them. - The Bushranger _{One ping only} 22:38, 22 November 2025 (UTC)[reply]

phab:T117884. * Pppery * _{it has begun...} 22:44, 22 November 2025 (UTC)[reply]

Oh, they "improved" it. Figures. - The Bushranger _{One ping only} 04:36, 23 November 2025 (UTC)[reply]

@The Bushranger You can make it more compact by adding the following to your Special:MyPage/common.js: if (mw.config.get('wgCanonicalSpecialPageName') == 'Userrights') {$('.oo-ui-fieldsetLayout-group .oo-ui-fieldLayout.oo-ui-labelElement').css('margin-top', 0)}. --Ahecht (TALK
PAGE) 17:00, 25 November 2025 (UTC)[reply]

Much better, thank you! - The Bushranger _{One ping only} 23:02, 25 November 2025 (UTC)[reply]

@Ahecht and The Bushranger: You don't need to jump through JavaScript hoops when it can be done in CSS:

.page-Special_UserRights .oo-ui-fieldsetLayout-group .oo-ui-fieldLayout.oo-ui-labelElement { margin-top: 0; }

this goes in Special:MyPage/common.css. --Redrose64 🌹 (talk) 23:21, 26 November 2025 (UTC)[reply]

@Redrose64, The Bushranger: Looks like something was changed in the software to force the top margin to 2px, so the CSS-only tweak doesn't work. That being said, having it set to 2px instead of 12px likely makes the tweak unnecessary anyway. --Ahecht (TALK
PAGE) 16:46, 1 December 2025 (UTC)[reply]

Well, it certainly  Works for me, I know because I tested it here. --Redrose64 🌹 (talk) 23:02, 1 December 2025 (UTC)[reply]

• See also phab:T410845. — xaosflux ^Talk 11:40, 3 December 2025 (UTC)[reply]

I've tried to mute User:JoeNMLC from spamming my talk page several times now. Why isn't it working? I don't want to be drilled messages by him. ♦ Dr. Blofeld 18:18, 29 November 2025 (UTC)[reply]

Muting doesn't apply to your user talk page. Izno (talk) 18:41, 29 November 2025 (UTC)[reply]

Dr. Blofeld - those messages are automatic created when I do a PROD (for articles without sources), and go to the article creator. Thanks for the feedback. Regards, JoeNMLC (talk) 19:40, 29 November 2025 (UTC)[reply]

Dr. Blofeld: See Help:Notifications#mute for what it does. If it works then you did not get a notificatin about JoeNMLC's above post which mentioned you but you got one for me. His posts to you like [1] were made with Twinkle and you cannot opt out of that. PrimeHunter (talk) 19:59, 29 November 2025 (UTC)[reply]

I think it's time then we allowed the option to opt out of Twinkle messages. To mute users should mean the ability to stop talk page messages from people. I have nothing against Joe and don't have an issue with him prodding articles which genuinely don't have adequate sourcing online, but I don't want to receive the prod notices. ♦ Dr. Blofeld 20:41, 29 November 2025 (UTC)[reply]

Twinkle is used for many things, e.g. escalating warnings. Disruptive users shouldn't be able to opt out of that. Others might opt out of Twinkle to avoid one type of post and then miss other types. PrimeHunter (talk) 21:05, 29 November 2025 (UTC)[reply]

I'm not a disruptive user. ♦ Dr. Blofeld 19:05, 2 December 2025 (UTC)[reply]

@Dr. Blofeld: I certainly didn't imply that. I just think there are too many problems with allowing users to opt out of Twinkle messages when Twinkle is used by so many users for so many different messages. We might allow a limited opt out like allowing users to opt out of prod messages but it sounds like significant work for a system very few would probably use. How bad is it to just remove or ignore the messages, and do you really never want to be notified about any article you have created? PrimeHunter (talk) 21:10, 2 December 2025 (UTC)[reply]

I have raised a PR for Twinkle to support recipient-level optouts for CSD/PROD/XFD notifications: https://github.com/wikimedia-gadgets/twinkle/pull/2251 – SD0001 (talk) 19:09, 2 December 2025 (UTC)[reply]

Thank you, appreciated. ♦ Dr. Blofeld 21:26, 2 December 2025 (UTC)[reply]

I wonder if it should use Template:Bots#Message notification opt out instead of a custom thing. Anomie⚔ 21:46, 2 December 2025 (UTC)[reply]

That's a fine system for bots. For gadget/user scripts, it's useful to have something that's easily detected client-side if the page is open ($('a.external[href*=optout\\.twinkle]')) or with an API call that has a small response (prop=extlinks with elquery param). Maybe the template could be made non-Twinkle specific, but if there's interest that can be done later as the advantage of not relying on the wikitext is that we can rename the template later, modify the external link it uses, etc. – SD0001 (talk) 11:28, 3 December 2025 (UTC)[reply]

It's not really the greatest system for bots either, but it's what we have. It works fairly well as a check when you're making an edit without using the "append a new section" feature, and it has both the advantage and disadvantage that it can't be (accidentally) transcluded from some other page. Anomie⚔ 12:48, 3 December 2025 (UTC)[reply]

On the list of articles I have created [2] there is Glynis Jones which is not my creation. The only edits I have made there are those two [3][4]. Is there any way how to remove Glynis Jones from the list? Ktrimi991 (talk) 02:01, 30 November 2025 (UTC)[reply]

Looks like you did create the page at one point: you created the redirect (in Special:PermaLink/852535838) by renaming the old version of the page to Glynis Jones (disambiguation). The history doesn't look like it because someone later did some history merging and splitting, which resulted in some of the disambiguation page edits you had moved to be merged with the redirect.

Apparently xtools identifies a "creation" by looking for the rev_parent_id field to be 0. I don't know of any straightforward way to reset this (since T183375 fixed preservation across deletion and undeletion). Anomie⚔ 02:34, 30 November 2025 (UTC)[reply]

Thank you for your explanation, much appreciated. The redirect that I created is supposed to be on the list of my redirects instead, not on the list of my articles. It seems that I will have to live with it. Ktrimi991 (talk) 03:57, 3 December 2025 (UTC)[reply]

I suspect that it doesn't show up on the "onlyredirects" list because it's not a redirect now. Anomie⚔ 13:05, 3 December 2025 (UTC)[reply]

Starting in October, WaybackMachine URLs are being added malformed a specific way:

https://web.archive.org/web/20250625020902//web/20250625020902/https://www.ssvulm1846.de/der-verein/historie/

They are being added by multiple editors. Although in one case, the same editor User:Bocanegra added them in multiple articles:

Special:Diff/1322943490/1324781064, Special:Diff/1320772985/1324780890, Special:Diff/1321924030/1324864220

Bocanegra says they are not using special scripts or tools or VE, just normal editing. Currently there are 19 cases (slow load), yesterday there were 15 (cleaned up a lot already). This is an active ongoing bug new instances added daily. Any thoughts? -- GreenC 15:19, 30 November 2025 (UTC)[reply]

Unless someone is cleaning ones as they show up, I don't see any that were added after the end of October, and none before mid-September ish. Izno (talk) 18:41, 30 November 2025 (UTC)[reply]

Weird. I cleaned up a bunch yesterday, down to 15, and today there are 19 27! The number keeps changing. Probably regex timeout. Anyone have a better search than this? insource:"//web/" insource:/\/\/web\// -- GreenC 19:04, 30 November 2025 (UTC)[reply]

This also hits a timeout but is probably marginally better since it dodges some obvious false positives. According to Help:Linksearch the externallinks table is available on Quarry. You can probably rustle up some SQL to find these (WP:RAQ can help if you don't know it).

Dates of introduction:

• September: 1, 2, 3, 4, 5, 6, 7, 8
• October: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10
• Early November: 1, 2, 3
• Late November: 1, 2

The source isn't VE from what I can see. I suppose it's possible to use Citoid via the toolbar rather than via VE so that is a possible cause. Otherwise, I suspect this is or was some copy-paste bug introduced by some browser or browser extension. Izno (talk) 17:44, 1 December 2025 (UTC)[reply]

Pinging a few of the editors that inserted these links recently to see if they remember how they did it: @KenL2001 (Special:Diff/1314815131), @Andykatib (Special:Diff/1323696641 and Special:Diff/1315329186), @Camilasdandelions (Special:Diff/1319672241), and @Bocanegra (Special:Diff/1315616423). --Ahecht (TALK
PAGE) 21:28, 1 December 2025 (UTC)[reply]

I'm not sure why that happened, I just went to here and put the grammy's link, then copied the link and pasted. Perhaps just the wayback machine's error or not.. Camilasdandelions (talk!) 21:57, 1 December 2025 (UTC)[reply]

I posted a query with Wayback Machine engineers to see if anyone recognizes it as a known problem. -- GreenC 03:41, 2 December 2025 (UTC)[reply]

Confirmed bug: according to Wayback engineers:

We had an issue from ~September 15th to ~October 5th related to the date URLs at the top adding an additional /web/timestamp

Izno posted some diffs above that post-date October 5, but the one's I checked appear be wikitext copied from other pages, or other parts of the article. -- GreenC 04:17, 2 December 2025 (UTC)[reply]

Thanks @Ahechtfor the heads-up. Lately, Internet Wayback Machine has sometimes been playing up. It works for some websites but certain websites like Reuters and Stuff don't allow it to copy their pages. Andykatib (talk) 22:16, 1 December 2025 (UTC)[reply]

I believe this is now repaired. The URLs were in over 100 articles, and probably over 400 links. If any new ones show up it will be from old diffs, such as a revert to an old version of the page. -- GreenC 19:50, 2 December 2025 (UTC)[reply]

I have a recurring problem where I nominate an article for deletion, and then don't get any notifications when comments are made or the discussion is closed. This would be a lot handier than bookmarking and coming back later, which is what I do now, as I often need to follow up with other cleanup, or sometimes there are questions that I could have answered. For example, on Wikipedia:Articles for deletion/강수연, there's no option to subscribe for new comments. If I go to Tools -> Subscribe, it seems that only subscribes me for new topics, but new topics are never created on AFD pages. Is there a good workaround for this, or is a feature request needed? -- Beland (talk) 03:14, 2 December 2025 (UTC)[reply]

Only solution is using level 2 headers at the moment. Sjoerd de Bruin (talk) 08:24, 2 December 2025 (UTC)[reply]

Hmm, it looks like level 3 headers are being used on each AFD page. It would actually be useful to also be able to subscribe or unsubscribe from level 3 sections, maybe? Sometimes a long discussion will split into multiple subthreads. -- Beland (talk) 08:44, 2 December 2025 (UTC)[reply]

You can vote for meta:Community Wishlist/W267. Nardog (talk) 09:00, 2 December 2025 (UTC)[reply]

Aha, that's what I was thinking was out there somewhere. Added myself as a supporter!

Theoretically if we changed XFD level 2 headers to level 1 and then level 3 to level 2, we'd work around this, but that might create a compatibility and re-templating nightmare? -- Beland (talk) 10:03, 2 December 2025 (UTC)[reply]

@Beland: Since every AfD is on its own individual page, you can do what I did: at Preferences → Watchlist, enable "Add pages I create and files I upload to my watchlist". This also works for MfD, but not CfD, FfD, RfD or TfD, on all of which several separate nominations share one daily page. For these, you would need to enable "Add pages and files I edit to my watchlist". --Redrose64 🌹 (talk) 21:44, 2 December 2025 (UTC)[reply]

Unfortunately, my watchlist has over 1400 pages and I almost never check it. (When I do, it's to purge the list of followup items from years ago.) -- Beland (talk) 21:48, 2 December 2025 (UTC)[reply]

Ah, but if I restrict viewing my watchlist to the Wikipedia namespace, it does actually produce a useful list of AFD pages I recently created. Thanks for the suggestion. -- Beland (talk) 22:31, 2 December 2025 (UTC)[reply]

I'm using the Vector 2010 skin in dark mode. Since returning from a few weeks away, I'm finding the caret in "reply" widgets is very dark grey (or maybe just very transparent) on black, making it nearly invisible. Which in turn makes it extremely difficult to make edits after typing. (Selection highlights in those textareas are also difficult to see, being navy or very transparent blue on black) In regular edit areas (such as my sandbox), it appears as its usual bright white, and selections the shade of green that I've configured. Has there been a CSS change recently? Though I can't find any caret-color rules using developer tools. I haven't edited my own user CSS lately, either. Using the latest Firefox on Mac (Sequoia), if that makes a difference. -- Avocado (talk) 16:43, 2 December 2025 (UTC)[reply]

Might be the syntax highligter. However, vector 2010 has no official dark mode support, so it is expected to vreak every once in a while and then you have to wait for a community memebrr to fix it (or not). —TheDJ (talk • contribs) 18:08, 2 December 2025 (UTC)[reply]

1. Not really sure how you fix but it’s desktop centric to use a first letter lowercase captcha when most phones default to capitalizing first letter. Proper English and all that. Anyway adds a level of friction on mobile

2. Who’s the captcha stopping? I didn’t test but that looked trivial to screen scrape - two simple words with distinct dark strokes ~2025-37933-19 (talk) 17:56, 2 December 2025 (UTC)[reply]

“Who’s the captcha stopping” the dumbest stuff, what is still a complete waterfall of bad faith contributions. But we might be switching to a invisble hcaptcha soon, so lets hope for that. —TheDJ (talk • contribs) 18:06, 2 December 2025 (UTC)[reply]

Also see Wikipedia:Village pump (WMF) § Replacing our CAPTCHA with a new bot detection service, part 2: editing and the links therein. Graham87 (talk) 05:49, 3 December 2025 (UTC)[reply]

The landing page after a successful page deletion, e.g.: https://en.wikipedia.org/w/index.php?title=User:Beland/Comparison_of_circulating_currencies&action=delete (which unfortunately only works once unless you recreate the page) has dark mode problems. It's title "Action complete" and then there's a box titled "Maintenance links" which has text like "Depending on the reason for deletion, you may want to remove any links to this page (articles | redirects)." All the body text in this box (except for blue links) is nearly impossible to read grey-on-grey in dark mode. I'm not sure where this text is controlled from. -- Beland (talk) 22:18, 2 December 2025 (UTC)[reply]

I don't see this issue with the supported dark mode for normal page deletions (which are at MediaWiki:Deleted-page-and-talkpage and/or MediaWiki:Deletedtext) based on the display there. I do see an issue with MediaWiki:Filedelete-success. Those are the only three pages I saw in a search with "depending on the reason for deletion". Izno (talk) 23:05, 2 December 2025 (UTC)[reply]

Ah, it looks like I tried to fix those before. The problem only shows up when the content is displayed in context after deletion, not when viewing the content on a standalone page. I tested this time and I seem to have actually fixed the first two. Your changes to the third page make it much better standalone; not sure how to test that as a sequence. -- Beland (talk) 23:20, 2 December 2025 (UTC)[reply]

Yup, just did the sequence on the suggested page and didn't see an issue. Izno (talk) 23:19, 2 December 2025 (UTC)[reply]

I'm looking at https://en.wikipedia.org/w/index.php?title=Special:EditWatchlist&namespace=0&offset=0%7CTwo-way&limit=500 and there's one page with an Arabic title. Because of a text order rendering bug, it shows up as "21(talk | history) [Arabic title] days left on your watchlist". Same problem with RTL title in Hebrew. I'm not sure where this interface is defined? -- Beland (talk) 22:49, 2 December 2025 (UTC)[reply]

This can't be fixed in the message. It probably merits an upstream task. Izno (talk) 23:00, 2 December 2025 (UTC)[reply]

Done: phab:T411561. Thanks for the diagnosis. -- Beland (talk) 23:07, 2 December 2025 (UTC)[reply]

What actually changed here? [5] — Martin (MSGJ · talk) 12:47, 3 December 2025 (UTC)[reply]

It was Es (Cyrillic). Nardog (talk) 12:50, 3 December 2025 (UTC)[reply]

Ah, okay, thanks. I knew I fixed it but didn't know how! — Martin (MSGJ · talk) 12:51, 3 December 2025 (UTC)[reply]

I copy-paste to https://r12a.github.io/uniview/ (not a Wikimedia tool) for such things. It indeed says "0421 CYRILLIC CAPITAL LETTER ES". In this case our own Special:Search/С would also have worked with a redirect to Es (Cyrillic). PrimeHunter (talk) 14:51, 3 December 2025 (UTC)[reply]

Greetings, The long-standing PetScan I've run like for months, is now showing error: Io(Io(Custom { kind: Uncategorized, error: "failed to lookup address information: Name or service not known" })). Against "Category - All articles lacking sources". If an expert here can investigate, that would be great. I know from in the past, sometimes, PetScan "magically" recovers, so I will try again tomorrow. (not urgent) Thanks. JoeNMLC (talk) 20:52, 3 December 2025 (UTC)[reply]

Yes! - PetScan now runs Ok. Cheers, JoeNMLC (talk) 22:31, 3 December 2025 (UTC)[reply]

Producing a tag with an attribute is easy: {{#tag:foo|txt|bar=baz}} generates <foo bar="baz">txt</foo>. But I'm writing a template where the attribute should be optional: depending on a template parameter, there should either be the attribute with a value or no attribute at all. I thought code like this should work (using a dummy condition here): {{#tag:foo|txt|{{#if:true|bar=baz}}}}. But it doesn't, the attribute is ignored: <foo>txt</foo>. It looks like {{#tag}} only recognizes attributes if the = character occurs directly in the value, even {{#tag:foo|txt|bar{{=}}baz}} doesn't work. So far, I can only think of two ways to make this work:

1. Wrap the whole code in an {{#if}} clause that contains two separate invocations of {{#tag}}. Of course, that leads to a lot of code duplication, since the invocations are identical except for the attribute.
2. Always generate an attribute, but give it a dummy name (and value, maybe) in the case where I don't actually want it: {{#tag:foo|txt|{{#if:true|bar|dummy}}=baz}}. This works in my case (the next parser phase seems to simply ignore the unknown attribute), but it feels a bit dirty.

Is there a better way to produce a tag with an optional attribute? — Chrisahn (talk) 20:57, 3 December 2025 (UTC)[reply]

Unfortunately there isn't. I usually do #2 if I am calling a template, but I prefer #1 if I am calling parser function or anything that is a black box. P.S. The way I do #2 is usually by adding a hash: {{my template|txt|{{#if:true||#}}bar=baz}}. --Grufo (talk) 00:12, 4 December 2025 (UTC)[reply]

I generally switch to generating it with Lua when the logic reaches this level of complexity. – SD0001 (talk) 03:40, 4 December 2025 (UTC)[reply]

Can't remember if I posted this here, but exactly what the question says. Does wikitext support this for CSS? My userpage previously used a lot of custom CSS and had a bunch of contrast issues depending on which colour mode a user is on, which I need to fix by creating overprecise CSS. thetechie@enwiki (she/they | talk) 22:30, 3 December 2025 (UTC)[reply]

Yes, your question has been answered. Izno (talk) 22:48, 3 December 2025 (UTC)[reply]

Not sure if this is the right place to post this, but I have an issue on my user page in which the userbox group does not work. If you expand it, it simply says {{{userboxes}}}. How do I fix this? thetechie@enwiki (she/they | talk) 22:31, 3 December 2025 (UTC)[reply]

@TheTechie: {{Userbox group}} recognises five named parameters: |collapse= |style= |title= |userboxes= and |footer= (it also recognises one positional parameter as an alias for |userboxes=). You're trying to use |title= (which is valid), |collapsed= and |content= (which are not). --Redrose64 🌹 (talk) 22:54, 3 December 2025 (UTC)[reply]

@Redrose64 Thank you. I think I was using Template:Userboxgroup, might be worth updating the documentation. thetechie@enwiki (she/they | talk) 20:23, 4 December 2025 (UTC)[reply]

No, you're definitely using {{Userbox group}}. {{Userboxgroup}} is a different template with different syntax. --Redrose64 🌹 (talk) 22:19, 4 December 2025 (UTC)[reply]

Why are there two templates with such similar names but different syntax that a typo of not hitting space could cause massive issues that aren't easily solvable? Should they be merged? ~212.70~ ~2025-31733-18 (talk) 04:58, 5 December 2025 (UTC)[reply]

Functionalities appear to be generally dissimilar. One should probably have a different name. Izno (talk) 05:54, 5 December 2025 (UTC)[reply]

Here are some links:

• Template:Userbox group (edit | talk | history | links | watch | logs)

  this one was created in 2017, initially in User: space, but not moved to Template: space until 2021

• Template:Userboxgroup (edit | talk | history | links | watch | logs)

  this one was created in 2019 and has always lived in Template: space

Judging by those, they have co-existed for more than four years. The one with prior claim to the name would at first glance be Template:Userboxgroup, but Template:Userbox group is maintained in synch with m:Template:Userbox group. --Redrose64 🌹 (talk) 23:23, 5 December 2025 (UTC)[reply]

Hello,

I've started making a game log for the 1996–97 Golden State Warriors season unfortunately it's not formatting the way it should and has some inexplicable | in it and I want those gone, can someone assist me with the game log formatting?

Thank you guys so much YachtSee (talk) 23:38, 3 December 2025 (UTC)[reply]

The documentation for {{NBA game log section}} was lacking a key instruction. I have fixed the documentation and the article. – Jonesey95 (talk) 01:44, 4 December 2025 (UTC)[reply]

Well That's annoying, the answer was right under my nose but it wasn't clear at the same time. YachtSee (talk) 04:25, 4 December 2025 (UTC)[reply]

2025 UNHRC Commission of Inquiry report on Gaza genocide is calling Template:Gaza genocide consensus citation bundle and one of the references isn't working in the article. I am not familiar with citation bundles I guess and have been unable to figure out how to fix the "Arab Center Washington DC" ref. Any help appreciated, I'm just trying to Wikignome my way through Category:Harv and Sfn no-target errors. I think the error has to do with the {{#invoke:cite|web that is missing from the Arab Center ref?, but am not certain and I sure as h*ll don't know how to fix it... I'd just like to get this article cleared from the error category. Thanks, Shearonink (talk) 05:08, 4 December 2025 (UTC)[reply]

Your problem has nothing to do with the {{#invoke:cite|web|...}} form of {{cite web}}.

Revert your edit at {{Gaza genocide consensus citation bundle}}. Add the {{cite web}} long-form citation to 2025 UNHRC Commission of Inquiry report on Gaza genocide § Sources – just like all of the other short-form references in {{Gaza genocide consensus citation bundle}}.

—Trappist the monk (talk) 14:12, 4 December 2025 (UTC)[reply]

Well, Trappist, I did basically post that I'm no expert... Thank you, I'm toddling off to fix it now. Always appreciate your expertise & advice. - Shearonink (talk) 15:16, 4 December 2025 (UTC)[reply]

Trappist the monk I tried to fix it and my poor skills and real life are interfering... I throw myself on the mercy of the court. - Shearonink (talk) 15:30, 4 December 2025 (UTC)[reply]

Hi, I was told to ask this question here. I tried to copy a GIF from The Heart Part 5 and put it on the Deep Voodoo article you accepted. It got removed for some kind of violation. Is there a right way to post that GIF on that article? Could I Do This? (talk) 16:00, 4 December 2025 (UTC)[reply]

That wasn't a technical issue, it was removed (bot assisted) for copyright issues. The primary reason is that the file is not free. You can follow up about it here: Wikipedia:Media copyright questions. — xaosflux ^Talk 16:17, 4 December 2025 (UTC)[reply]

Thanks for the explanation! Could I Do This? (talk) 16:19, 4 December 2025 (UTC)[reply]

See [[6]] The contributions for User:Could I Do This? send you to the contribs for the nonexistent user User:Could I Do This. The ? is being removed. Is this a known bug? Best wishes, Macaw*! 18:29, 4 December 2025 (UTC)[reply]

Note: I think this is because the url interprets the ? as the start of a query string. We probably need to make it escape it to %3F automatically as https://en.wikipedia.org/wiki/Special:Contributions/Could_I_Do_This%3F works Best wishes, Macaw*! 18:35, 4 December 2025 (UTC)[reply]

Macaw*, where are you getting that link from? Navpopups/Moremenu both seem to handle this just fine. — Qwerfjkltalk 18:41, 4 December 2025 (UTC)[reply]

Yup, Special:Contributions/User:Could I Do This? seems to work just fine. — xaosflux ^Talk 19:11, 4 December 2025 (UTC)[reply]

A raw ? in a URI is used to declare a query, not a bug so much as a feature. — xaosflux ^Talk 19:14, 4 December 2025 (UTC)[reply]

The XTools gadget I think. it adds a link to the users contribs for the user who most recently edited that page Best wishes, Macaw*! 20:00, 4 December 2025 (UTC)[reply]

Macaw*, I can't see any links like that in XTools, but there's a link at the bottom of xtools for reporting an issue. If you do so, make sure to include where the link is. — Qwerfjkltalk 20:34, 4 December 2025 (UTC)[reply]

@Macaw*: Please say from the beginning where you see a reported problem. The contributions link works in all places I have tested but you load 68 scripts in User:Macaw*/common.js. I tracked it down to this script by Opencooper:

importScript('User:Opencooper/lastEdit.js'); // Backlink: User:Opencooper/lastEdit.js

PrimeHunter (talk) 22:53, 4 December 2025 (UTC)[reply]

Thank you for the ping. My script indeed did not link this userpage correctly. Now fixed.

Regarding the confusion, part of this might also be due to both of us having User:PleaseStand/userinfo.js installed, which also has a similarish message. I've been meaning to make it clearer for my userscript that the date is for when the userpage was last edited rather than when the user last edited. Edit: Done. Opencooper (talk) 23:27, 4 December 2025 (UTC)[reply]

style="background:linear-gradient(to bottom, gray 50%, no color 50%) how can one side be colored and one side be colorless?

for example

Rafael Ronen 14:40, 5 December 2025 (UTC)[reply]

I have adjusted the code above to possibly do what you want. You can also use "transparent" instead of white, but it can cause problems in dark mode. – Jonesey95 (talk) 15:33, 5 December 2025 (UTC)[reply]

What is a good way to query all abuse logs (also known as edit filter log) of a user on all wikis on which they have created a local account? I know I can use mw.ForeignApi, but I was wondering if there's a better way. NguoiDungKhongDinhDanh 06:27, 6 December 2025 (UTC)[reply]

In one place, no. You would need to first fetch all their attached accounts, then query each project's abuselog individually. — xaosflux ^Talk 20:42, 7 December 2025 (UTC)[reply]

Hello, I just tried to edit a page and added a new reference, however when I hit "publish changes", it said "Your edit includes new external links. To protect the wiki against automated spam, we kindly ask you to solve the following hCaptcha: This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.", which is to be expected. However, I can't complete the CAPTCHA as it is not appearing at all on my screen. I am using a 5th Gen iPad (2017) on iOS 14.6. Many websites don't work due to my outdated iOS, however this is the first time I have had an issue with Wikipedia, and I published changes successfully only a month or two ago. ~2025-38416-80 (talk) 15:00, 6 December 2025 (UTC)[reply]

Forgot to mention (but it won't let me change it because of said issue!), I'm using the Wikipedia website (not the app). ~2025-38416-80 (talk) 15:13, 6 December 2025 (UTC)[reply]

There is a new CAPTCHA see Wikipedia:Village pump (WMF)#Replacing our CAPTCHA with a new bot detection service, part 2: editing. -- Guerillero ^{Parlez Moi} 16:42, 6 December 2025 (UTC)[reply]

Have you tried submitting the form even without the hCaptcha showing, and seeing if it publishes your edit?

This might be falling into an uncommon situation that we're aware is possible, but will go away next week when we tighten the configuration slightly. EMill-WMF (talk) 17:36, 6 December 2025 (UTC)[reply]

I've just tried again and still no luck. Every time I hit "publish changes", it just refreshes the page. No error code or anything. I do all my browsing in "private" mode (Apple's version of incognito), I'm assuming that's not relevant, but maybe that could have something to do with it? Thanks for your reply anyway. ~2025-38416-80 (talk) 18:29, 6 December 2025 (UTC)[reply]

@EMill-WMF see phab:T411927 - this is a significant bug, as it is impacting a core user function: adding content to the project. — xaosflux ^Talk 20:40, 7 December 2025 (UTC)[reply]

UPDATE: I managed to find a workaround! If I use the mobile layout, the CAPTCHA is visible and I can publish changes as usual. They're a few visual glitches with text in mobile mode, but it mostly functions normally. Still doesn't answer why I had this problem in the first place, but maybe it can provide some clues. ~2025-38416-80 (talk) 19:54, 6 December 2025 (UTC)[reply]

• There is a bug going on, phab:T411927 has been opened on this. There are 2 work arounds: (a) click "publish" AGAIN, then it should pop the hcaptcha dialog. (b) try using a free account, sign up at Special:CreateAccount. — xaosflux ^Talk 20:39, 7 December 2025 (UTC)[reply]

When I'm logged in, I get a sticky header overlapping the top of the browser window as I scroll down.

If I click a link to a subsection within an article that's derived from the title of that article- in this case Prince_Rupert's_cube#Noperthedron_and_non-Rupert_polyhedra- the start of the section I want to read appears just below the sticky header, as one would want. (In other words, it makes an allowance for the sticky header and offsets the anchored section from the top of the window).

However, if I click a link to a link defined via {{anchor}}- in this case, {{anchor|nopert}} and Prince_Rupert's_cube#nopert- the subsection title and content immediately following it are obscured by the sticky header (i.e. allowance is *not* made for the sticky header in this case).

This applies even when the {{anchor}} is placed between the opening and closing "==" (or whatever) in the section title.

This is annoying, particularly as links to section titles are prone to breaking whenever they are changed and anchors are less likely to be broken in this way.

This behaviour happens both with my usual browser, Firefox 145, and using Microsoft Edge. (Since the latter is now Chrome-based, I assume it happens with Chrome too, though I haven't checked that as I don't have it installed).

Ubcule (talk) 16:53, 6 December 2025 (UTC)[reply]

I substed the anchor per the template's documentation. Did that help at all? – Jonesey95 (talk) 19:54, 6 December 2025 (UTC)[reply]

@Jonesey95: Thank you for drawing my attention to that- I probably should have seen and read that before.

Oddly, however, it doesn't seem to have solved or made any different to the problem at hand. Ubcule (talk) 23:34, 6 December 2025 (UTC)[reply]

This has been reported already at phab:T406114. – Ammarpad (talk) 20:14, 7 December 2025 (UTC)[reply]

Moved to Wikipedia:Reference desk/Computing § no sound on windows 10

 – — DVRTed (Talk) 05:39, 7 December 2025 (UTC)[reply]

The latest run of Special:WantedCategories features three redlinked categories — Category:Airport, Category:Election and Category:Sports venue — that are each being autogenerated by strange behaviour on stub templates.

In all three cases, what's happening is that the template coding is failing to generate or include the actual category specified by category1= in the template coding, and is instead basing the category name on the contents of tempsort1= — for example, the Airport category is being generated on {{NewBrunswick-airport-stub}} by the code

| category1 = New Brunswick building and structure stubs
| tempsort1 = Airport

so that the category "Airport" is replacing the expected Category:New Brunswick building and structure stubs.

In each case, this is only affecting category1= and tempsort1=. But if I try to fix it by removing tempsort1=, it restores category1= but then suddenly starts whiffing category2= and tempsort2= instead. And it also warrants note that none of these are new stub templates, either: they're all long-standing ones that weren't doing this nonsense at all before now. It also, in each case, appears to only be affecting the categorization of the template itself as a template, and does not appear to be transcluding the wrong categories onto articles, as Bathurst Airport (New Brunswick) is still in Category:New Brunswick building and structure stubs, and has not been smuggled into Category:Airport.

So since this is absolutely beyond my abilities to figure out or fix, could somebody try to determine what the heck's going on? Thanks. Bearcat (talk) 16:04, 7 December 2025 (UTC)[reply]

I would say that this is a matter for Template talk:Asbox. --Redrose64 🌹 (talk) 16:32, 7 December 2025 (UTC)[reply]

As far as I can tell, there's some weird garbage collection going on with respect to Module:Buffer. At one point Module:Article stub box does (v[1] and Buffer(v[1]) or attention):_in(v.k):_(v.t):_str(2, nil, nil, '|'). The :_in(v.k) only weakly references the Buffer(v[1]), so if garbage collection happens to occur sometime before :_str(2, nil, nil, '|') stringifies the whole thing then the category name gets lost, the joining gets confused into losing the |, and we wind up with just [[Category: Airport]] rather than [[Category:New Brunswick building and structure stubs| Airport]]. If garbage collection doesn't happen to occur, it works fine. Which also makes it very hard to determine whether an attempted fix really fixed it or just happened to avoid triggering a GC at the wrong time. Anomie⚔ 17:11, 7 December 2025 (UTC)[reply]

With some experimentation, and comparison of Template:NewBrunswick-airport-stub (which fails) with Template:NewfoundlandLabrador-airport-stub (which works), the significant difference is the use of {{flag icon}} in the former. If I alter ... {{flag icon|New Brunswick|size=30px}} ... to ... [[Image:Flag of New Brunswick.svg|border|30px]] ... it works as intended. --Redrose64 🌹 (talk) 17:28, 7 December 2025 (UTC)[reply]

Sorting templates by date that are transcluded by these pages, I see an innocuous-looking change to Template:Yesno. Is it possible that this change caused this issue? I don't see how that could be possible, but given the intricate discussion at the template's talk page, I'd say there's a chance. – Jonesey95 (talk) 17:46, 7 December 2025 (UTC)[reply]

If it did, I suspect it's only indirectly, by changing the details of how much memory is used when and therefore when the garbage collection is triggered. Same for the flag thing. When I was trying to debug it in Module:Article stub box, I found that simply inserting (literally) mw.log( "???" ) in the right place would make the TemplateSandbox preview stop showing the problem. Anomie⚔ 18:01, 7 December 2025 (UTC)[reply]

Offtopic, but by god is the code of Module:Buffer basically impossible to understand! * Pppery * _{it has begun...} 23:57, 7 December 2025 (UTC)[reply]

I had a similar reaction. Anomie⚔ 00:04, 8 December 2025 (UTC)[reply]

Hello. I am having an issue with content translation: I want to translate the page ƛ̓ from French to English (link), but it keeps saying something similar to this:

- BᴏᴅʜıHᴀᴙᴩ (talk, contributions) 23:04, 7 December 2025 (UTC)[reply]