Wikipedia:Village pump (technical)

 Policy Technical Proposals Idea lab WMF Miscellaneous 
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.

Add AutoCiteWikidata as gadget?

Automatic citations are now easier via Wikidata: See the AutoCiteWikidata gadget. Discussed here on Diff: "making automatic citations connected with Wikidata"

This should be a default gadget option without users having to discover this user page. See the discussion at T289287. – SJ + 19:02, 30 October 2026 (UTC)

The likelihood that we will be expanding the reach of {{cite Q}} I estimate is about 0. So, it has no chance of being a default gadget any time soon. Izno (talk) 21:03, 30 October 2026 (UTC)
Cite Q is and always has been an ill-behaved and underdeveloped template that has caused CITEVAR issues. Just to check if anything had changed, I clicked on four articles at random from its "What links here" list, and found Cite Q CITEVAR problems and related inconsistency at Frances Abington, Edible mushroom, Atrial natriuretic peptide, and William Dampier. Four out of four. This template being used in over 17,000 articles is a problem for people who care about consistent presentation of citation information. – Jonesey95 (talk) 21:57, 30 October 2026 (UTC)
Two of your four articles do not even use Cite Q for citations. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits; 23:03, 30 October 2026 (UTC)
Frances Abington uses it in the Wikipedia:External links section, and Atrial natriuretic peptide uses it inside a template in the ==Notes== section. WhatamIdoing (talk) 23:33, 30 October 2026 (UTC)
Frances Abington and Atrial natriuretic peptide had simple author fixes at the Wikidata end, Edible mushroom was complaining about the now defunct citeseerx parameter in cite journal, and William Dampier doesn't appear to have any problems I can see. — Jonathanischoice (talk) 05:26, 9 November 2026 (UTC)
"Simple author fixes at the Wikidata end" is an oxymoron. Nothing on Wikidata is simple and fixes on Wikidata are often reverted because they were inconsistent with some other database somewhere else. —David Eppstein (talk) 01:01, 13 November 2026 (UTC)
That's utter nonsense. I've been making many such changes lately. They are very simple to do and none have been reverted. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits; 08:48, 13 November 2026 (UTC)
This has not been my experience. Jonathanischoice (talk) 11:19, 13 November 2026 (UTC)

Some issues. Cite Q only exists in 78 languages while cite journal is in 237. This is going to be an issue for those of us involved in translation.
When one looks at the Wikitext like <ref>{{cite Q|Q38897648}}</ref><ref>{{cite Q|Q104102440}}</ref> one has no ability to see the metadata. Ie what journal is this, what was the year of publication, all critical to determine reliability. One has to go back to the article text to see the reference which makes editing difficult.
Would need global templates and would need the lake of metadata in wikitext mode solved before this template should be used IMO. Doc James (talk · contribs · email) 22:32, 30 October 2026 (UTC)

Cite Q is available to any project which wishes to use it and works in any language which Wikidata supports - which is far more than 237.
Your second paragraph is addressed in the template documentation.
While global templates would indeed be good, we do not need them for Cite Q to work. This too is addressed in the template documentation. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits; 22:45, 30 October 2026 (UTC)
I see the drawbacks of cite Q as greater than the benefits. I have raised these issues for years. Doc James (talk · contribs · email) 22:56, 30 October 2026 (UTC)
Odd, the template's talk page archive search only finds your name once. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits; 23:01, 30 October 2026 (UTC)
Yah 9 years ago I raised the issue of no metadata in the wikitext and it appears not solved. Doc James (talk · contribs · email) 23:05, 30 October 2026 (UTC)
"This too is addressed in the template documentation." Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits; 23:09, 30 October 2026 (UTC)
"Addressed", in the meaning of discussed? But not "addressed" in the meaning of solved? Or am I missing something.
Sure we could at the Q to cite templates. But that is not this.
The Cite Q template has many of the same issues as the Cite doi template that was deprecated. Doc James (talk · contribs · email) 23:14, 30 October 2026 (UTC)
I think this would be good - Cite Q's quite a mature template now, and it's widely used across many different language Wikipedias. There's been ongoing conversation in particular re Doc James's points in T289287. Thanks. Mike Peel (talk) 20:25, 2 November 2026 (UTC)
Cite Q still breaks multiple different things, imports broken cites and improperly formated references. It use shouldn't be expanded until it's properly fixed. Beyond that editors shouldn't have to go to a different project just to change something on Wikipedia, but that's a different discussion. -- LCU ActivelyDisinterested «@» °∆t° 14:27, 5 November 2026 (UTC)
I look forward to your RfC on ceasing to use Wikimedia Commons. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits; 10:52, 8 November 2026 (UTC)
If I want to format the way an image is displayed on Wikipedia I don't have to edit Commons. If that was the case I would argue for images to be uploaded locally, as that would be a ridiculous situation. -- LCU ActivelyDisinterested «@» °∆t° 11:42, 8 November 2026 (UTC)
If you want to change how a citation using Cite Q is formatted you can do so on Wikipedia.
If you want to crop or rotate (by a few degrees) an image transcluded from Commons, that is where you must do so.
If you want to replace an image transcluded from Commons with one where the white-balance is adjsuted, that is where you must do so.
If you want to change the text label, map shading or boundaries, or bar chart percentages or colours of an SVG image transcluded from Commons, that is where you must do so. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits; 14:06, 8 November 2026 (UTC)
You can not change the details that cite q imports from wikidata, the example of commons is not the same. That some editors like editing wikidata as well is not a reason to impose it in other editors. -- LCU ActivelyDisinterested «@» °∆t° 22:43, 8 November 2026 (UTC)
It was you who chose to bring up the issue of formatting.
Svg images such as those I gave as examples import data from Commons, which cannot be changed, so yes, that example is the same.
That some editors like editing Commons as well is surely equally not a reason to impose it on other editors, so I'm back to awaiting your RfC... Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits; 22:49, 8 November 2026 (UTC)
It is obviously not the same, not even a little bit. Again if editors want to edit wikidata they can, they shouldn't impose it on others. -- LCU ActivelyDisinterested «@» °∆t° 22:51, 8 November 2026 (UTC)
Who is imposing Wikidata on whom, exactly? If you don't like editing Wikidata, then don't use Cite Q, use something else. I like editing Wikidata, and see it as a self-improving ever-incrementing thing much like Wikipedia itself, and so Cite Q is something I very much enjoy building and using, and many other editors I know do in fact like to use it too. So I'd much prefer it if you didn't go around undoing many people's hard work by, for instance, converting Cite Q to other citation templates. Such an action would make a lot of people I know very unhappy. Besides, rather than all this unhelpful and somewhat hysterical invective, I would rather that you were more constructive, and perhaps instead list what you don't like about it, so we can improve it. In the last two months, I've fixed almost all of the items on @Headbomb's laundry list (archived), so if you could kindly itemise exactly how Cite Q makes you sad, I'd be more than happy to fix those things as well. — Jonathanischoice (talk) 04:06, 9 November 2026 (UTC)
Anyone using cite Q on anyone who doesn't want to also edit on Wikidata, and wants to modify the the citation being used in Wikipedia. I don't convert cite Q that would be a violation of CITEVAR, something that editors who go around adding cite Q to articles appear to miss. Something that makes a lot of editors I know very unhappy. Issue with the template, one that doesn't have full community support per the box at the top of its own documentation, are continually ignored or handwaved, go back to its talk page if you want examples or the many discussions on it. -- LCU ActivelyDisinterested «@» °∆t° 13:07, 9 November 2026 (UTC)
So, a case of WP:IDONTLIKEIT then. Let me know if you have anything I can actually work on. — Jonathanischoice (talk) 19:32, 9 November 2026 (UTC)
No. A bot that regularly turns all Cite Q templates into regular local citation templates would be a good thing though. We should limit the times people need to edit Wikidata to correct errors on enwiki to the absolute minimum, not burden articles with errors like " {{Cite Q}}: QID parameter must be supplied as "Q" followed by digits, e.g. Q12345 (help): Missing first/last names in Wikidata" (apparently this error happens in 3000 of the 18000 articles which use Cite Q, so not a rare occurrence). Fram (talk) 14:43, 5 November 2026 (UTC)
The missing name errors were added recently as a result of much better name handling. We are working on the backlog; it was over 4000 when the changes went in, and will hit zero in a few weeks at the current rate. Fixing these errors also improves the data in Wikidata, so you could always roll your sleeves up and help, rather than complain about it here. I find the idea of converting Cite Q to local templates very short-sighted and strange. — Jonathanischoice (talk) 03:33, 8 November 2026 (UTC)
Just to add, it appears that as of today there are no articles that are in the category Category:Cite Q - invalid QID. EatingCarBatteries (contribs | talk) 07:03, 8 November 2026 (UTC)
A bot to make to convert these would be a good idea. -- LCU ActivelyDisinterested «@» °∆t° 11:47, 8 November 2026 (UTC)
I disagree, that would be a really dumb and short-sighted idea. Jonathanischoice (talk) 13:40, 8 November 2026 (UTC)
Using cite Q is a dumb and stupid idea, the problems if which haven't been thought through. -- LCU ActivelyDisinterested «@» °∆t° 22:45, 8 November 2026 (UTC)
No, per Fram and ActivelyDisinterested. Mike Christie (talk - contribs - library) 15:05, 5 November 2026 (UTC)
No, if someone vandalises a Wikipedia reference I can very easily correct it. If someone vandalises a Wikidata reference I won't even notice it. Wikidata still has the issue of BLPs being connected to pornography despite not being pornographic actresses Maybe you should solve that issue before attempting to push more Wikidata rubbish onto WP? Traumnovelle (talk) 04:33, 7 November 2026 (UTC)
Cite Q is a blight and should be discouraged everywhere. One can only hope it gets deprecated and banned to deepest pits of the abyss, much like {{cite doi}} and {{cite pmid}} were. Headbomb {t · c · p · b} 15:03, 7 November 2026 (UTC)
@Traumnovelle: You just enable Wikidata in your enwiki watchlist, and revert vandalism there if needed (which is rare in my experience)? I've checked the Wikidata item you linked to, and can't see any signs of it being connected to pornography?
@Headbomb: personally I wish that Cite Journal was discouraged everywhere. Having worked in academia for 20 years now, Wikipedia is pretty much the only time I've had to manually write out a reference (or use a tool to hard-code it in the article), rather than just using a bibcode and a database that I can maintain centrally (e.g. preprint -> journal article) - and that's what Wikidata now provides us with here.
In general I wish we could avoid rhetoric and disinformation when talking about Wikidata, and focus more on the pros and cons... Thanks. Mike Peel (talk) 22:13, 7 November 2026 (UTC)
If you do enable Wikidata edits, you'll immediately see that there's onehelluvalot of irrelevant junk going through before you spot something that deserves attention. Stuff like descriptions in some language you simply cannot comprehend. Or "badges" - which seem to be something like featured article. It just clutters up the watchlist. In short: can't see the wood for the trees. --Redrose64 🌹 (talk) 22:26, 7 November 2026 (UTC)
Yah there was a request to be able to watchlist only those parts of Wikidata used specifically on Wikipedia. Right now I think if one adds Wikidata to your watchlist it shows every single change to the Wikidata item. Not sure were that request is at. Doc James (talk · contribs · email) 22:28, 7 November 2026 (UTC)
That behaviour was changed years ago as far as I'm aware - have you tried it recently? Thanks. Mike Peel (talk) 22:32, 7 November 2026 (UTC)
Perfect, will have another look. It has been years since I tried seeing Wikidata in my watchlist because every new addition of a translation would appear. Doc James (talk · contribs · email) 23:11, 7 November 2026 (UTC)
"rather than just using a bibcode and a database" , just write {{cite journal|bibcode=2002...}} or {{cite journal|doi=10.1151/...}} and let citation bot expand the reference for you. Headbomb {t · c · p · b} 22:33, 7 November 2026 (UTC)
This is a new feature for me - and there's no mention of this at {{Cite journal}}? How does this citation bot keep things up-to-date when the reference changes? Thanks. Mike Peel (talk) 22:37, 7 November 2026 (UTC)
What do you mean by "when the reference changes"? References are fairly static for journals. Doc James (talk · contribs · email) 23:12, 7 November 2026 (UTC)
There's two parts to this. The first is the change I experience the most as an active researcher: references change from preprints to journal references. That's probably less relevant for enwiki since it lags behind. The other is when references become outdated (withdrawn/replaced), e.g., see Wikipedia:WikiProject Medicine/Cochrane update. This is something I've been supporting through Wikipedia:WikiProject Medicine for many years now through my bot as an interim measure, but I'd love to see transitioning to a proper solution such as Cite Q in the future. Thanks. Mike Peel (talk) 23:21, 7 November 2026 (UTC)
RetractionBot does at least some of this. LittlePuppers (talk) 23:29, 7 November 2026 (UTC)
If the bot instead (or additionally) updated Wikidata by adding retracted by (P5824), ‎has expression of concern (P14891) and corrigendum / erratum (P2507) statements to the relevant journal articles, then Cite Q will automatically transclude the relevant warning templates into the citations, e.g. {{Cite Q|Q29030043}}
Estruch, R.; Ros, E.; Salas, J.; et al. (2013). "RETRACTED: Primary Prevention of Cardiovascular Disease with a Mediterranean Diet". The New England Journal of Medicine. 368 (14): 1279–1290. doi:10.1056/nejmoa1200303. PMID 23432189. Wikidata Q29030043. (Retracted, see doi:10.1056/nejmc1806491, PMID 29897867, Wikidata Q58419365. If this is an intentional citation to a retracted paper, please replace {{Cite Q|...}} with {{Cite Q|...|retracted-intentional=yes}}.)
— Jonathanischoice (talk) 04:24, 9 November 2026 (UTC)
Preprints shouldn't be cited to begin with. Retractions are rare and there are better ways to address that. Traumnovelle (talk) 07:28, 8 November 2026 (UTC)
RetractionBot looks really useful, but let's approach the edits from that tool from the general approach taken in this conversation so far. And sorry @Samwalton9 and Mdann52: in advance. First off, it's only working on enwiki - a far cry from the minimum standard here of the 78 languages that Cite Q supports, and of course, 1 is very much less than 237. It's making random edits like removing https in favour of http, and removing unused parameters. I think we all want things to work on-wiki first rather than relying on external tools, and that's where Cite Q helps: everything is on-wiki either here or on Wikidata, and you can track and fix any issues on-wiki. Thanks. Mike Peel (talk) 21:48, 8 November 2026 (UTC)
Preprints are automatically upgraded to cite journals by the bot. At least for {{cite arxiv}}, {{cite biorxiv}} and {{cite medrxiv}}. Headbomb {t · c · p · b} 11:40, 9 November 2026 (UTC)
I shouldn't have to do that. I removed the item because its obviously an issue for a BLP to be connected to pornography. The more integrated Wikidata becomes with Wikipedia the more desirable it becomes to vandalise it. Traumnovelle (talk) 07:27, 8 November 2026 (UTC)
Ah, this edit? That was definitely a bad edit, and thanks for reverting it. It doesn't have anything to do with Cite Q, though. With your last sentence, there's a trade-off with visibility: the more visible something is, the more quickly any vandalism will get reverted. That's kinda fundamental for how Wikipedia operates. Thanks. Mike Peel (talk) 21:29, 8 November 2026 (UTC)
The old "vandalism isn't really an issue on Wikidata" claims... Since 5 November, thanks to Wikidata, the infoboxes on Catalan, Welsh, Basque, Norwegian, Romanian, Hungarian, Swedish, Greek, ... all claim that Blake Lively is married to Justin Baldoni since 2012. Apparntly the high visibility (famous person, shown on many wikis) did nothing to catch this rather blatant BLP violation for over a week now. Lower visibility vandalism remains much longer, as witnessed by the 1412 children of Fyodor Vasiliev on his Spanish article: Wikidata vandalism from september which stayed for nearly 2 months and which remains visible on eswiki due to caching delays.
Did you know that Heinrich Himmler's birth name is Natanael Cano Monge? At least three languages have received this info since 4 November.
Trusting Wikidata to rapidly correct even highly visible or obvious vandalism is as naive now as it was 10 years ago. Fram (talk) 13:40, 13 November 2026 (UTC)
The 4 November edit you link to for Himmler shows the Monge birth name being added as deprecated. If malformed templates on certain Wikipedias are displaying deprecated values, that's a local issue for those Wikipedias to fix. It wouldn't happen on this Wikipedia (and if if did, it would rapidly be corrected). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits; 14:00, 13 November 2026 (UTC)
I support adding this as a non-default gadget but oppose making it default. Clearly to what degree to use Cite Q bitterly divides the community and has for a very long time. The best way to reflect that divide is to let people who want to use it enable it while not forcing those who don't to do so. * Pppery * it has begun... 23:38, 7 November 2026 (UTC)
I agree and thank you, that's the first sensible thing I've heard all day. — Jonathanischoice (talk) 04:27, 9 November 2026 (UTC)

New share button coming to mobile Wikipedia

Hello, I'm Maryana, a WMF Product Manager. We’re planning to add a new way to share Wikipedia articles on mobile web: a dedicated Share button and Share Card.

Screenshot of what the new share button on mobile Wikipedia looks like. The new button is to the right of the (locked) edit button in this screenshot.
Screenshot of the share card that appears after tapping the share on mobile Wikipedia. Tapping to Share pulls up your phone’s native Share sheet to ensure we don’t promote any specific third-party app or website.

Why are we doing this?

People share Wikipedia articles with each other through text and social media, but our mobile experience doesn’t encourage this behavior. With Wikipedia traffic declining, we want to help bring readers to our platform by providing additional information and attribution. Share buttons on articles are a WP:PERENNIAL request, and we’ve built this feature to allow users to choose whichever social or messaging apps on their phones that they would like to use to address the concern of promoting any specific third-party app or website.

This work is based on a May 2026 Reader Growth team experiment on mobile Wikipedia (arwiki, zhwiki, frwiki, viwiki, enwiki) to show this new Share button/card to a sample of readers. Findings from this experiment indicate that additional traffic was brought in by people clicking on Share Cards shared on external platforms, bringing an estimated potential 25 million additional pageviews to Wikipedia per year.

What risks have we considered?

We have held two calls with Wikipedians on Discord this year to discuss this feature and hear any concerns or risks, which we have worked to address:

How we are planning to proceed

  1. Today through November 8th: we are inviting all Wikipedians to test this feature for themselves on their wiki. To test: on a mobile device, add ?useformat=mobile&sharecard=1 to the end of any Wikipedia article URL. Please feel free to report any issues here or on this task in Phabricator: phabricator:T442968.
  2. On November 9th: if all looks good and there are no outstanding major issues, we will deploy this feature on mobile web to all Wikipedias. (This feature will not be available on desktop.)
  3. After November 9th: we’ll continue to monitor for any bugs, issues, and any enhancements suggested by communities. We will also consider future iterations of the share card to test.

Please let us know if you have questions or feedback, and we encourage you to give the feature a try. Thank you! Maryana Pinchuk (WMF) (talk) 14:01, 2 November 2026 (UTC)

I don't think I fully understand the functionality you are trying to create here – the new share button in my testing just creates an image composite. I wonder where traffic from people clicking on Share Cards comes from, because the image does not automatically become a link when shared. If someone posts the card in discord, I can't navigate to the article unless I type out the shortened URL or just search for the article title, which is significantly worse functionality than you get from just posting the link directly (which automatically embeds an image and short description). Your assertion that this generated thousands of article shares and pageviews in testing is plausible, but not impressive considering enwp alone gets on the order of 250 million page views daily. Do you have any idea how much more external traffic is coming from direct links, or how the CTR compares? I almost always use the mobile app when reading on my phone if I can help it, so I already have a very functional share button, but I have a feeling that anyone who does use this feature will actually be driving less readership than they would if all they had was a URL. —Rutebega (talk) 10:20, 3 November 2026 (UTC)
Hi @Rutebega, thanks for your question and apologies for not making this clearer in the original post: when someone taps the big blue "Share" button on the Share Card, what's shared is the image you see in the screenshot above plus a link to the article (which we've instrumented using our standard practice of establishing provenance on traffic coming from different platforms/products).
To the right are a few more screenshots I took to show you what this means concretely. What you're seeing here is:
  • After I tapped Share on the Cat article, I selected to share as a text message.
  • When I did this, it opened up a new text message in my text message app, and the Share Card image, as well as a snippet of the lead and a link to the article (that's the box at the bottom of the text message in the second screenshot to the right, below the lead text, that says "Read more on Wikipedia") are automatically added here already.
  • Note: This is what it looks like to share to iMessage on an iPhone – on Android or if sharing to other apps, this will look slightly different because they all take in the "share" metadata framework we're using slightly differently, but in general a link is shared along with the visual card.
This is how we know that people were coming back to Wikipedia via this feature during the small-scale experiment we ran earlier this year – other links to Wikipedia don't have this unique provenance parameter, so the only way for a pageview on Wikipedia to have this parameter is if it came from a click on a link shared via Share Card (or I guess someone could have manually copied the specific URL parameter we used and appended it to a Wikipedia URL, but that would be... implausible ).
Apologies again for the confusion. Does this help clarify? Maryana Pinchuk (WMF) (talk) 01:57, 4 November 2026 (UTC)
Does this mean the issue of images being badly cropped is solved? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits; 22:06, 8 November 2026 (UTC)
Hey @Pigsonthewing: yes, we're looking into how we might improve image cropping more generally. It's not an easy/quick fix, but we're investigating some options! Maryana Pinchuk (WMF) (talk) 00:50, 10 November 2026 (UTC)
While I'm sure this is useful for people who don't know how to copy URLs or who use the app, I find that it clogs up the interface more. Making buttons more cramped together means they're even more difficult to press. Many useful tools are hidden behind the ellipsis, and I don't want a button I won't ever use to take up valuable screen space. Heck, I can't even watchlist pages anymore without clicking the ellipsis.
While I appreciate the thought that has gone into this, especially for readers, I think it's a net negative for me. How can I disable it?
P.S. I've had the same problem with the "saved articles" button - won't ever be using it, so I don't want it there. Advice on how to disable that would be appreciated as well. --not-cheesewhisk3rs ≽^•⩊•^≼ ∫ (pester • FAC) 17:37, 10 November 2026 (UTC)
@Not-cheesewhisk3rs: If you're on a desktop, use ⇧ Shift+Alt+W to toggle watched/unwatched. --Redrose64 🌹 (talk) 15:44, 11 November 2026 (UTC)
I'm not on desktop, but thank you for the reply anyways. --not-cheesewhisk3rs ≽^•⩊•^≼ ∫ (pester • FAC) 15:52, 11 November 2026 (UTC)
I've just found that in Vector 2022, ⇧ Shift+Alt+W has lost some functionality. If the watch/unwatch tab is visible, or if it's in the ellipsis menu and that menu is open, all that ⇧ Shift+Alt+W does is to move focus to that tab or menu item - there is no toggling. You need to then press ↵ Enter to actually toggle the setting. The automatic toggling still works in Vector Legacy, MonoBook etc. although the popup no longer disappears in seconds - it now persists until dismissed or you navigate away. WP:ITSTHURSDAY, I think. --Redrose64 🌹 (talk) 08:26, 13 November 2026 (UTC)
@Redrose64 This is a bug related to the new Watchlist popup which allows you to add labels. I believe this bug is T432368, which we hope to fix soon. Samwalton9 (WMF) (talk) 12:42, 13 November 2026 (UTC)
@Not-cheesewhisk3rs thanks for chiming in here. We’re thinking about and testing potential ways to improve the top navigation experience for both logged in and logged out readers (including via the MinMin experiment and other experimental design improvements to reduce top navbar clutter and make sure the right actions are available at the right time). Clarifying question: are you typically logged in when you're browsing Wikipedia on mobile, and do you typically use an Android or an iOS device? The icons you get in the top navigation bar change depending on logged in/out state and which device you're on, so this info helps me get a better sense of what you're seeing/reacting to. Maryana Pinchuk (WMF) (talk) 21:31, 12 November 2026 (UTC)
@MPinchuk (WMF): I edit on mobile. (This is a mobile edit, for example.) The feature is only frustrating because I'm a logged-in contributor. I've got both an Android and iOS device, and I use Wikipedia in my browser.
Essentially, what I'm seeing is that the top bar icons are "language", "save", "history", "edit", "share" and the ellipsis. Now that the "watch" function has been moved into the ellipsis, I can no longer tell from a glance whether I'm watching a page or not, and watchlisting a page is also more difficult because things in the ellipsis options are so close together. The spacing of stuff is really annoying on a phone, because small, clustered things are more difficult to click on precisely.
I think there should be some option for logged-in users to disable the "share" and "save" functions because they take up crucial space. That is all. More customisability for mobile editing makes it easier to work with. I also think that there should be a fix for some common bugs, such as the bug where the website freezes and I have to reload the page and I lose the edit which I was working on (because MinervaNeue doesn't save it in that case). But that is an entirely different can of worms. --not-cheesewhisk3rs ≽^•⩊•^≼ ∫ (pester • FAC) 22:05, 12 November 2026 (UTC)

leads with indented formulas are fragmented on mobile

On desktop, the lead of NADPH dehydrogenase is:

In enzymology, a NADPH dehydrogenase (EC 1.6.99.1) is an enzyme that catalyzes the chemical reaction
NADPH + H+ + acceptor ⇌ NADP+ + reduced acceptor

But on a mobile device, or in mobile view on a computer when the browser window is narrow like it would be on a mobile device, the infobox intercedes between the incomplete first sentence and the formula, leaving the article starting with an incomplete sentence fragment:

In enzymology, a NADPH dehydrogenase (EC 1.6.99.1) is an enzyme that catalyzes the chemical reaction
[infobox]

The lead of NAD(P)H dehydrogenase (quinone) has the same problem. I could just edit these articles to make the formulas part of the lead sentences, but a) I wonder if there's a better solution, and b) I suspect there may be more cases like this: perhaps someone knows how to look for any, and then fix them all systematically. -sche (talk) 03:01, 4 November 2026 (UTC)

I guess the trick we need is to add a line break before the formula, but keep it marked up as a part of the previous paragraph, so that the mobile site doesn't split it. Here's one way to do it, using <chem display="block"> markup:

In enzymology, a NADPH dehydrogenase (EC 1.6.99.1) is an enzyme that catalyzes the chemical reaction NADPH+HA++acceptor↽−−⇀NADPA++reduced acceptor

However, Wikipedia:Manual of Style/Chemistry#Line equations advises against it, on the basis that it looks bad. (IDK, it looks good to me.)
You could also achieve a similar effect using {{pb}} and {{pad}} instead of a real paragraph break:

In enzymology, a NADPH dehydrogenase (EC 1.6.99.1) is an enzyme that catalyzes the chemical reaction

 NADPH + H+ + acceptor ⇌ NADP+ + reduced acceptor

But I'm not sure if these templates are supposed to be used outside of talk pages. Matma Rex talk 18:48, 4 November 2026 (UTC)
The "looks bad" is font mixing, which I clearly see happening in your example. The wiki-text prose is sans-serif. The equation that is in wiki-markup matches that. The <chem display="block"> is serif instead. DMacks (talk) 04:37, 9 November 2026 (UTC)
Unfortunately, neither this (1) nor this (2) fixed the problem. {{pb}} like this (3) and {{pad}} like this (4) didn't fix the problem either, nor did this (5), removing the line break but leaving the 'block indent' template. The only thing I've found that stops the infobox from breaking the line in half is this (6), just putting the formula as part of the sentence without any indentation or template. I feel like that solution might not work in cases where the formula is particularly complex and/or requires special formatting or templates, but I could be wrong. Should this be reported at Phabricator, with the argument that the software shouldn't be putting the infobox in the middle of the sentence in a situation like (3) or (4), or do we think they'll tell us it's not their problem, it's that the entry should be formatting the text in some other way? -sche (talk) 00:42, 13 November 2026 (UTC)
The reason this happens is because mobile moves the infobox after the first paragraph. The first paragraph ends before the formula. You can either rewrite the lead or accept the results. as I don't anticipate the developers will change that behavior. Izno (talk) 01:42, 13 November 2026 (UTC)

Phase 2 Semantic Search A/B test live on web: help us test!

Hi all,

I’m writing to let you know that the Reader Growth team’s A/B test of "semantic search”, or natural language search, capabilities on the web version of Wikipedia went live today. We are trying this to make it easier for people to find the information they’re looking for on the wikis so that, as we face declining pageviews, Wikipedia can be a better destination for learning and discovery. Here is an example search results page that the treatment group could see; you can also try more semantic queries on this page (please check that you have &mpo=semantic-search-for-web:hybrid-srp at the end of your URL to see semantic results if you do multiple searches).

We increasingly have been hearing from readers that they want to be able to ask questions to Wikipedia. This makes sense, since more and more people are getting used to using chatbots. But we also know that it is important for Wikipedia content to be presented in the way that volunteers wrote it. So in this feature, readers will ask natural language questions – but rather than generating answers, it returns the excerpts from Wikipedia articles that may answer their question. So far, as we’ve shown this to volunteers, it sounds like we’re on the right track! (but of course I want to hear what you think).

We first posted about Phase 2 a couple weeks ago, and before that we shared Phase 1 (A/B test on mobile apps) in February and Phase 0 (Exploration) in January.

Check that Phase 2 thread for more details, including research about the gaps in our current search experience, the results of a previous semantic search test on the apps, the differences between the apps and the web, and metrics we are looking at for this current test. The project page also has much more information about all of our thinking, research, and progress in this area.

The left screenshot illustrates the current experience of searching on Wikipedia mobile for "who invented airplanes." The screenshot on the right shows the experience asking the same question in the experimental semantic search treatment.

What this test is:

Semantic search means retrieving information based on the meaning, concepts, or contextual relationships of someone’s query. Currently Wikipedia search does not support semantic search, and instead fully relies on lexical retrieval, which is based on exact search terms, or keyword matching.

This test will be shown to 1% of desktop and mobile English Wikipedia readers typing in the search bar, who will see the existing "Search for pages containing..." call to action (CTA) as usual below the typeahead suggestions. Clicking that CTA, or hitting enter on their query, will take readers in the test's treatment group to an advanced search results page that will include semantic results. This page will also include a survey question asking whether users found the results helpful, and inviting them to write out more feedback.

I also want to note that the search results page in the treatment is not as fully featured as the regular search results page (e.g., it doesn’t have the red link to create a new article, and it doesn’t have the search results from sister projects). That’s not a long-term design decision; rather, we built a simple page to conduct and learn from this test.

The test will be turned off in December. If early results are promising, we will come back to discuss them together and what we think should happen next.

What we’re asking for your help with:

We have done some early work identifying risks and edge cases, particularly related to queries where semantic results could be easily misinterpreted or even harmful. We’re thinking about 1)  situations in which people’s searches could bring up some of the more sensitive content on the wiki, and 2) situations where our search algorithm might present results that appear to answer the query, but in a way that does not seem neutral. For example, we know an issue exists with block quotes – sometimes the search returns a block quote from a specific point of view that is presented like it is a neutral article excerpt, which is misleading. This is an improvement we’re working on (it is a technical challenge for the search algorithm to identify block quotes appropriately).

As you try out various queries, please help us be on the lookout for risks we may not be aware of yet. If you find any, please share a URL and screenshot of the results, along with a description of your concerns, at the Information Retrieval Phase 2 project talk page. We think community testing of this feature will be crucial to build something useful for our billions of readers while also taking care not to cause harm or create confusion. Thank you for your help. EBlackorby-WMF (talk) 22:19, 10 November 2026 (UTC)

I clicked the link to try queries but it doesn't work, at least on my end. The link takes me to https://en.wikipedia.org/w/index.php?title=Special:SemanticSearch&mpo=semantic-search-for-web:hybrid-srp but all I see on there is a link to "Switch to classic search" in the middle of the page. – Scyrme (talk/solidarity) 22:55, 10 November 2026 (UTC)
@Scyrme -- thanks for trying it! Yes, so from that page, try typing a question into the search bar and pushing enter/search (e.g. "What is the difference between a tuba and a sousaphone?") MMiller (WMF) (talk) 22:58, 10 November 2026 (UTC)
I see! Sorry, it wasn't clear initially. I thought the usual search bar would exit the semantic search testing page and take me to classic search results, and expected another search bar within the page area where the "Switch to" button is.
Seems to work well so far, even when I try strange questions (eg. why do fish dig? → received a snippet about fish that burrow in mud) or questions that contain wrong assumptions (eg. why do cats bark? → received snippets about cat vocalisations). – Scyrme (talk/solidarity) 04:12, 12 November 2026 (UTC)
Hello! I just tried out the query "ea nasir" with https://en.wikipedia.org/w/index.php?title=Special:SemanticSearch&search=ea%20nasir&ns0=1&limit=10&sort=relevance&noredirect=, and it seems to have a bug where clicking on the "did you mean" link just takes me back to the same page. GrinningIodize (you just lost the game) (talk) 00:38, 13 November 2026 (UTC)
Update: It also happens in the classic search engine. GrinningIodize (you just lost the game) (talk) 00:41, 13 November 2026 (UTC)
Thanks @GrinningIodize! Your experience with the "did you mean" (DYM) feature is partly due to our not yet having tailored the suggestions for semantic searches, as you also discovered when you tried the same query in classic search and got the same suggestion. We've discussed this a bit as a team and would be interested in updating DYM for semantic searches as a future improvement. I know the Search team also has been investing over time in the existing DYM logic as well and can pass on this example to them so we at least can avoid the ouroboros of suggesting the same correction for the thing that didn't need to be corrected :) SherryYang-WMF (talk) 17:24, 13 November 2026 (UTC)
Happy to help! Thanks for the quick response. GrinningIodize (you just lost the game) (talk) 18:27, 13 November 2026 (UTC)
Thank you and your team for working on this. In my opinion, this has very high potential.
At the risk of repetition, I would like to bring up articles about current events. Information in them can be outdated or unreliable, but if we extract snippets from them, we likely need to indicate their currency in the snippets.
If I have more concerns, I will bring them up. Thank you all once again! LightNightLights (talk • contribs) 18:27, 16 November 2026 (UTC)

Parsoid failure?

I'm copyediting Taxation in Finland, and the page rendering went berserk – narrow columns and long, single-letter columns which are bolded (possibly section headers). I was going to go on wikibreak until whatever was wrong was fixed when I saw a "Switch to legacy parser" in the page tools; clicking that makes the page render normally. It would be nice to know what's going on; I have to switch to the legacy parser after copyediting each section, which is time-consuming. In solidarity, Miniapolis 23:10, 10 November 2026 (UTC)

Unable to reproduce —TheDJ (talk • contribs) 14:12, 12 November 2026 (UTC)
@TheDJ:, Firefox is my preferred browser; I wonder if it's browser-related. In solidarity, Miniapolis 18:42, 12 November 2026 (UTC)
And I was happy to see a Parsoid opt-out option in my preferences: Editing → Developer tools. In solidarity, Miniapolis 23:54, 12 November 2026 (UTC)

A new one on logging in...

So, the first time I clicked on "log in", I got a text page about a parserURL (or some such) failure. Second click of log in worked, I've seen this before, it happens. But when I logged in, I got a message saying "Authentication was successful but your session has expired. Please click "Log in" to recover it.". That's new. More meatballs in the backend spaghetti code? - The Bushranger One ping only 03:27, 12 November 2026 (UTC)

We're looking into this at T444791. Matma Rex talk 17:47, 13 November 2026 (UTC)
@Matma Rex: For the record, just had it happen again (although this time there wasn't the initial parserURL thing, just went straight to "successful but"). - The Bushranger One ping only 21:31, 14 November 2026 (UTC)
And just had "invalid return URLtoken" on first time clicking 'log in'. - The Bushranger One ping only 03:56, 17 November 2026 (UTC)
Me too, on the "Authentication was successful but your session has expired. Please click "Log in" to recover it." thing, about 12:30 today (UTC). --Redrose64 🌹 (talk) 15:43, 17 November 2026 (UTC)

Comparison template

Is there a comparison template that orders lists by value. Say, if there are 4 values one higher than the order, it would list them as 1 being the highest and 4 the lowest? I want to automate the process for calculate "standings" (right-most col) in {{4TeamRR-TennisWide}}, for example, 2025 WTA Finals – Doubles#Liezel Huber Group. 8rz (talk) 01:09, 13 November 2026 (UTC)

Check out Module:AutosortTable. the Stefen 𝕋ower 01:12, 13 November 2026 (UTC)

.. page have been removed from your watchlist.

Today I notice that when I unwatch a page by clicking the "unwatch" tab from a recent diff of that page, the browser pops up a box says "[page name] and its talk page have been removed from your watchlist", with a big Undo button. This is both annoying and unnecessary - I can see it's been removed because the "unwatch" tab changes to "watch", and if wanted to undo it I would just click that tab again. Can we please not have the box - or at least make it optional.

I'm using MonoBook, Firefox 115.45.0 on Windows 7. Mitch Ames (talk) 12:05, 13 November 2026 (UTC)

Maybe related to this? As well as the new popup when unwatching, I also see a larger, more persistent box when I click "watch". Mitch Ames (talk) 12:14, 13 November 2026 (UTC)

Yep, these are related - my team just rolled out new watch star popover behaviour to make it easier to add labels to your watched items. Previously, the same popover was displayed as a toast notification, the main change is that the location has moved so that it's closer to the Watch star that you just clicked. Additionally, after unwatching you can now Undo the action, which preserves your expiry date and labels, if they were set. I see what you're saying about already seeing that it's unwatched. Maybe the popover with Undo should only be displayed if you had an expiry or label configured? I worry it might be confusing to show it some times and not others, curious what others think! Samwalton9 (WMF) (talk) 12:46, 13 November 2026 (UTC)
It is somewhat regrettable that the unwatch popup doesn't seem to have a unique ID or class distinct from the watching popup so it could be hidden in one's CSS. Nardog (talk) 12:59, 13 November 2026 (UTC)
Yes that is unfortunate. You can hide both popups with this in your CSS:
.cdx-popover__backdrop .mw-watchstar-WatchlistPopup {display:none;}
If you do this but temporarily want them on a page (the watch popup adds features you may sometimes want) then you can add ?safemode=1 to the url. User:PrimeHunter/Safe mode.js makes a link under Tools to do it. PrimeHunter (talk) 13:57, 13 November 2026 (UTC)
You could also middle-click the watch star to open the action=watch page on a new tab. As in https://en.wikipedia.org/w/index.php?title=Wikipedia:Village_pump_(technical)&action=watch. This is how I was adding labels to pages until today but you can also use it to add expiries if you want to hide the popup. Warudo (talk) 17:48, 13 November 2026 (UTC)
@Mitch Ames: You mentioned doing it from a diff. If the url already has a ? then add &safemode=1 instead. The script automatically picks the right one. PrimeHunter (talk) 14:02, 13 November 2026 (UTC)
Another option if you have an article link to hover over would be to enable Wikipedia:Tools/Navigation popups via the Preferences → Gadgets → Browsing option.
I generally use the Action → un option in the hover window to unwatch pages as I review my watchlist, and it's pretty convenient (and appears to bypass the new "Undo" functionality). — SirOlgen (talk) 19:53, 13 November 2026 (UTC)

"Watch"/"Unwatch" tab shenanigans again

Some time back this was briefly a thing, but then it went away. Just now I discovered that clicking the "Watch"/"Unwatch" tab at the top of a page produces a popup dialog box confirming it with an "Undo" button, directly below the tab, vis-a-vis the previous brief "this happened" box in the upper right that faded away. This change is, frankly, obnoxious and undesirable for me - is there any way to turn it off? - The Bushranger One ping only 22:23, 13 November 2026 (UTC)

The Bushranger, please see #.. page have been removed from your watchlist. just above. —⁠andrybak (talk) 22:55, 13 November 2026 (UTC)
Thank you. I've used the css there. I did like the little 'quickly fading box' in the upper right that it previously did, but... - The Bushranger One ping only 23:19, 13 November 2026 (UTC)

New tool: Wikipedia2Book – printable PDF books from Wikipedia articles

Hi all, I'd like to share a tool I've been developing: Wikipedia2Book, hosted on Toolforge.

Since the Book Creator PDF export was retired, there has been no simple way to turn a set of articles into a single printable book. Wikipedia2Book fills that gap:

Privacy: the server is stateless – no account, no tracking, no book stored server-side. Your book stays in your browser and can be exported/imported as JSON.

The interface is available in 12 languages. Source code (AGPL-3.0): https://github.com/gmoulard/wikipedia2book – there is also an API: https://wikipedia2book.toolforge.org/docs

Disclosure: I'm the developer. Feedback, bug reports and suggestions are very welcome, here or on GitHub. 474D6F756C617264 (talk) 13:10, 13 November 2026 (UTC)

Wikidata not updating?

I'm pretty sure that if you move a page, the WikiData entry is supposed to update automatically. But consider these moves by Extraordinary Writ (talk · contribs): d:Q1869108 still points to the old page name, with the result that Pi bot (talk · contribs) removed the {{Commons category}}, which should not have happened since c:Category:London Underground S7 and S8 Stock exists and is linked from d:Q1869108. Has something changed to cause the WikiData entry to not be updated? --Redrose64 🌹 (talk) 20:09, 13 November 2026 (UTC)

It should update automatically. This was a more complex move, though, since the pagename already existed. It looks like the deletion of London Underground S Stock didn't result in the sitelink being removed from Wikidata, so when the page was moved to that title it didn't update. Maybe it all happened a bit too quick for the systems to keep up with? I've already fixed this on Wikidata. Maybe @Lydia Pintscher (WMDE): might know more? Thanks. Mike Peel (talk) 20:15, 13 November 2026 (UTC)

In my experience, the search bar does work on mobile devices. However there's a glitch where the FIRST time you tap the search bar (that is set up to show results with a particular PREFIX) on a page such as Wikipedia:Vital articles/Level 4 or Wikipedia:Help desk, you are taken to a blank page containing the search bar only that says "Search Wikipedia". This search bar will search the entire site, but only in the article namespace. Then if you press the back arrow, and click the search bar a SECOND time, you will stay on the same page instead of being taken to a blank page, and you can search within the given PREFIX space. This is my experience with Google Chrome on mobile, and this has been a glitch with all search bars searching with a prefix for a long time. ~2026-60081-75 (talk) 00:01, 14 November 2026 (UTC)

This also happens to me with talk-page search-bars. This issue has been reported and fixed before, but I do not have the bug discussion at hand. LightNightLights (talk • contribs) 10:50, 14 November 2026 (UTC)
I believe this is phab:T402078 ("InputBox on mobile skin (Minerva) loses focus on first click, jumping to main search bar"). HTH. Quiddity (WMF) (talk) 21:15, 15 November 2026 (UTC)

Bypassing linkrot with a template parameter

Want to add an #ifexist function to {{draw links}} so when a non-existent tennis event page is called with the |tour= parameter via the template it displays Singles – Doubles in plain text instead of [[page title – Singles|Singles]] – [[page title – Doubles|Doubles]] to avoid linkrot per WP:REDLINK. The |tour= param variant is only used on 2026 ATP Tour and 2026 WTA Tour season tennis results pages to separate/distinguish it from namesake yearly templates, namely {{2026 ATP Tour}} and {{2026 WTA Tour}}.

Tried {{#ifexist:{{{1}}}|...Singles}} for Singles, Doubles and Mixed doubles which doesn't seem to work (see diff). I want the last testcase in Template:Draw links/testcases to display Singles - Doubles only for the "2027 US Open" event and not be redlinked. 8rz (talk) 13:06, 14 November 2026 (UTC)

@8rz: The main page 2027 US Open does exist (as a redirect) so I have changed the testcase to 9999 which works as you want. PrimeHunter (talk) 16:29, 14 November 2026 (UTC)
I think the sandbox code also needa adjusting to account for non-existent page. See the testcase with the black background with the |white= parameter. It displays erroneously; it should display (S, D), not Singles – Doubles. That needs fixing before the template's code is synced with the sandbox. 8rz (talk) 16:43, 14 November 2026 (UTC)
additional tests (testcases 3 & 4) give the opposite results of what I want. |tour= with |white= displays (S, D) and |white= gives Singles – Doubles. I need it it display the opposite. White is only to be used in navs' bottom row for color contrast as (S, D), whereas tour is to be used only on yearly tennis pages where the full Singles – Doubles version is required (wikilinked only when page exists, otherwise display in plain text). 8rz (talk) 17:18, 14 November 2026 (UTC)
@8rz: I have repeated the code to choose words or letters for the case where ifexist is false. Templates often get an annoying amount of repetition because they cannot assign variables. I haven't handled the scenario where tour and white are both set like in your 2027 Australian Open test case. Does that ever happen for real? PrimeHunter (talk) 05:41, 15 November 2026 (UTC)
Well, the 2nd conditional gets the job done. The white & tour testcase I added it just for testing purposes; there's no real case where one'd use both (white's for navs, tour for articles). Thanks for the help. Much appreciated. 8rz (talk) 14:17, 15 November 2026 (UTC)
@PrimeHunter, could you be so king enough to update the template's code so I don't have to post an edit request. Thanks. 8rz (talk) 14:28, 15 November 2026 (UTC)
Done. PrimeHunter (talk) 02:39, 16 November 2026 (UTC)

New tool for comparing language editions

Hi all, at Junction 2026 in Helsinki we built Parallax, a read-only tool that puts the Finnish, Swedish, German, English, Russian, Estonian and Ukrainian editions of an article next to each other sentence by sentence. For each statement it shows how the other editions put it and when each of them added, reworded or removed it, with a link to that revision. You can also pick a date in the past and get the comparison as it stood then. A separate list collects statements that one edition removed while the others still have them, together with the edit summary of the removal. It works for any article that has a Finnish version (a new one loads in a minute or two and keeps one state per year, while the preloaded Winter War has every revision).

Sentences are matched with a multilingual embedding model (bge-m3) and Gemini decides whether two of them say the same thing and translates them into English. There's also a page where you paste a chatbot answer and see which editions back each of its statements. Pasted text goes to Gemini and the checked answer is stored so it can be opened again. No user names are stored.

It isn't on Toolforge but runs on our own server, which stays up for the next few months. We built it as a hackathon entry and nothing more is planned right now, but if people find it useful we could talk about taking it further. The code is on GitHub under MIT. TimKicker (talk) 12:52, 15 November 2026 (UTC)

Editing content in templates via VE - where do things stand?

It's a very old issue that content inside templates is difficult to edit in Visual Editor, involving opening a template dialogue box, finding the parameter, and editing wikitext within a little text box. It's a bit of a pet peeve for templates that include a lot of content, like the many lists that use {{div col}}. Just curious if there have been developments since I last checked like 8 years ago? :) — Rhododendrites talk \\ 00:47, 16 November 2026 (UTC)

I'm afraid nothing has moved on this front. The old task requesting this feature is T52355. Matma Rex talk 11:24, 16 November 2026 (UTC)
It's very disappointing how much a feature used by newcomers on tons of Wikipedia languages has almost zero development going on, apart from edit checks I don't remember anything major the last few years. Sjoerd de Bruin (talk) 18:19, 16 November 2026 (UTC)

Bugged latex in the dark mode of the vector skin

I'm reporting that latex got bugged in the dark mode of the old vector skin. It used to be fine just several week/months ago for me, but now it's illegible. I haven't tested it in the new skin yet.

Here is how it looks for me

Broken latex in the dark theme of the vector skin

Tim Ocean (talk) 14:30, 16 November 2026 (UTC)

try uninstalling extensions in chrome I had this issue and that was the cause of it ~2026-60601-85 (talk) 15:04, 16 November 2026 (UTC)
I'm using Mozilla. What extensions specifically? Tim Ocean (talk) 15:53, 16 November 2026 (UTC)
When reporting a problem, always link to an example page and try to follow the other advice in the edit notice that appears when you edit this page. – Jonesey95 (talk) 16:06, 16 November 2026 (UTC)
(school change thing so same person) most of these are base html markup, and not a part of Wikipedia. Wikipedia's dark mode implementation acounts for LaTeX already, so something must be modifying it. it just happened to be extensions for me I think. ~2026-60615-70 (talk) 16:23, 16 November 2026 (UTC)
I looked at Arithmetic progression, the apparent article in question in dark mode using Brave browser on Mac OS, logged out, default Vector 2022 skin, and the equations look fine to me. It looks like the OP is reporting a problem with Vector, which does not have a MediaWiki-supported dark mode, as far as I know. Maybe they are using Wikipedia:Dark mode (gadget), in which case problems should be reported at the talk page for the gadget. – Jonesey95 (talk) 18:01, 16 November 2026 (UTC)
The dark mode in your preferences is a gadget that is best described as unsupported, especially since the rollout of dark mode native for Vector 2022 and Minerva. Any other dark mode you might be using is probably not something we have control over. Izno (talk) 18:06, 16 November 2026 (UTC)
And seeing as you have no user javascript installed, it is either the relevant gadget or some sort of dark reader extension. I would guess you're using darkreader but it might be another. You can see what extensions you have by following these instructions. Either way, we cannot fix an issue in one of those extensions here. Izno (talk) 18:11, 16 November 2026 (UTC)
I don't know what rollout means. Please, be less cryptic.
I had had darkreader installed, but I had it disabled. I uninstalled it whatsoever and restarted Mozilla.
The problem is stil out there.
Native Wikipedia vector dark mode.
I'm using exclusively dark mode native to Wikipedia Vector. I even turned off dark mode in Mozilla - nothing helps except for switching to Vector light mode. Tim Ocean (talk) 18:53, 16 November 2026 (UTC)
You are using the "skin" (appearance setting) called "Vector legacy (2010)", with the Gadget (listed under Preferences -> Gadgets) called "Dark mode toggle" enabled. That gadget is described at Wikipedia:Dark mode (gadget). That gadget is increasingly incompatible with viewing Wikipedia pages. At the top of that page, you can see a notice that says, in part, "This gadget is not recommended for enabling dark mode on Wikimedia sites."
You have a few choices. One choice is to use the normal light mode instead (i.e. uncheck the gadget in your Preferences). Another is to go to Preferences -> Appearance and choose the "Vector (2022)" skin, the default, newest, and best-supported skin. That skin has a built-in dark mode that is supported. The page Arithmetic progression works fine with that skin in its native dark mode. The new Vector 2022 skin will take some getting used to, because menu and table of contents items that you are used to have been moved to different places. – Jonesey95 (talk) 19:29, 16 November 2026 (UTC)
I switched to Vector 2022. Latex is still bugged in the dark mode.
Bugged latex in the Dark mode of Vector 2022
Tim Ocean (talk) 21:53, 16 November 2026 (UTC)
If you haven't already, you need to disable the "Dark mode toggle" gadget and instead use the "Appearance" sidebar (or, if you have hidden it, the glasses icon at the top) to turn on dark mode. Otherwise you won't be able to use the native dark mode and will see this message: You're using a dark mode gadget that interferes with this feature. Disable the gadget to use dark mode. OutsideNormality (talk) 22:05, 16 November 2026 (UTC)
I had to turn off both the gadget and some Core styling for dark mode gadget... but it finally works. Thanks for help and farewell Vector 2010 :(( Tim Ocean (talk) 23:07, 16 November 2026 (UTC)
Rollout: when a bunch of software updates is released. Like when Firefox got upgraded from version 159 to version 160 a few days back. --Redrose64 🌹 (talk) 21:42, 16 November 2026 (UTC)
This is a general problem with Vector 2010. (I also use Firefox, but I don't think it's browser specific.) I lived with illegible black-on-black formulae because I found them less annoying than the narrow text of Vector 2022 or the retina-burning default white background.
I just added .MathJax {color: white;} to my common.css file, which seems to have solved the problem. This change, of course, would cause problems without dark mode, and may cause problems I've not yet noticed even with dark mode. Certes (talk) 23:26, 16 November 2026 (UTC)
@Certes Have you tried Vector 2022 with Wide mode (click the eyeglasses button on the top and choose "Wide")? If you do that and choose "Hide" on the table of contents and tools sidebar it's even wider than Vector 2010. --Ahecht (TALK
PAGE
)
18:33, 17 November 2026 (UTC)
I'd tried Wide but not noticed the option to hide the TOC sidebar. (It may not have existed then.) Thanks; I'll have another look. Certes (talk) 23:43, 17 November 2026 (UTC)

Tech News: 2026-47

MediaWiki message delivery 21:22, 17 November 2026 (UTC)

Prod in userspace

The latest run of the WP:USERNOCAT report features a user's .js settings page appearing in three proposed deletion tracking categories, even though prod is not for use in userspace. The prod was placed there by the creator themselves, with the rationale "I accidentally made this", so it probably should just be deleted, but prod isn't the correct process for that. However, I don't have the necessary privileges to edit other editors' js pages in order to get it out of the categories, so could somebody who does have those privileges deal with the page some way or other so that it isn't just left sitting on the report as a permanent speedbump for the next week? Thanks. Bearcat (talk) 00:40, 18 November 2026 (UTC)

LaundryPizza03 left a note and the author corrected it to a CSD template. LittlePuppers (talk) 00:55, 18 November 2026 (UTC)