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.
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 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.
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).
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)
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)
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)
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 BushrangerOne ping only 03:27, 12 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 BushrangerOne ping only 21:31, 14 November 2026 (UTC)
And just had "invalid return URLtoken" on first time clicking 'log in'. - The BushrangerOne 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)
I got the same message just now. There was no button that just said "log in" apart from one for CentralAuth login, nor an option to reenter my username and password. Thinking that maybe something hadn't loaded properly or that it would restart the process entirely, I refreshed that webpage, but instead it logged me in as though nothing had happened. Andrew11374265 (talk) 00:51, 20 November 2026 (UTC)
@Andrew11374265: "Log in" isn't a button, it's a link at top right. --Redrose64🌹 (talk) 09:34, 20 November 2026 (UTC)
A glitch with search bar
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)
Issue (redlinks), unfortunately, still not fixed. Not sure why the testcases are displaying properly, but real-life cases aren't. See User:8rz/sandbox#Dl2 test
{{Dl2|2026 lorem ipsum|MS=1|WD=1|tour=1}}
Singles–Doubles {{Dl2|1987 Stockholm Open|tour=1|X=1}} Mixed doubles {{Dl2|2026 atp finals|S=1|D=1|tour=1}}
Singles–Doubles {{Dl2|2026 aTp finals|S=1|D=1|tour=1}}
Singles–Doubles {{Dl2|2026 ATP Finals|S=1|D=1|tour=1}} Singles–Doubles {{Dl2|2026 ATP Finals|S=1|X=1|tour=1}} Singles–Mixed doubles {{Dl2|2027 ATP Finals|D=1|X=1|tour=1}} Doubles–Mixed doubles {{Dl2|2027 ATP Finals|D=1|X=1}}
(D,X) {{Dl2|2027 ATP Finals|S=1|D=1|X=1}}
(S,D,X) . 8rz (talk) 12:16, 18 November 2026 (UTC)
:After additional testing figured out the source of the problem. Digits followed by a lowercase character (2026 atp finals, 2026 aTP Finals) hide redlinks, otherwise (2026 ATP Finals) they are displayed. 8rz (talk) 12:40, 18 November 2026 (UTC)
nvm, that's not it. 8rz (talk) 12:43, 18 November 2026 (UTC)
@8rz: It only tests whether the main tournament article like 1987 Stockholm Open exists. That was your own code so I assumed that's what you wanted. If a tournament doesn't have mixed doubles then don't use X=1. PrimeHunter (talk) 12:02, 19 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?:) —Rhododendritestalk \\ 00:47, 16 November 2026 (UTC)
I'm afraid nothing has moved on this front. The old task requesting this feature is T52355. Matma Rextalk 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)
Thanks. Disappointing indeed. Such a common issue. Perhaps PPelberg (WMF) knows what's up with this one? Seems like a perennial complaint the WMF would receive from newbies and long-timers alike. Is there some major technical blocker? —Rhododendritestalk \\ 03:41, 19 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.
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 2022Tim 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
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Updates for editors
At wikis where Mentorship is configured, permanently blocked users will no longer be assigned a new mentor when their original mentor quits. Temporarily blocked users will still be assigned a new mentor, in line with existing Mentorship practices.
VisualEditor's citation tool will be changed later this week to always open the "automatic" tab (Citoid) instead of remembering the last tab used by an editor. This change is made to support inexperienced editors who rely on the automatic citation option to create references, but often struggle to find it again after clicking on the "manual" or "re-use" tab.
One new wiki has been created: a Wikivoyage in Malayalam (voy:ml:)
Videos in articles and on Commons are slowly starting to use adaptive streaming for playback instead of being delivered as one large file at a fixed quality (example video). This means that video quality will adjust automatically based on a reader’s internet connection, ensuring videos start more quickly and buffer less often. It also places less load on our infrastructure. The rollout will expand gradually to all videos over the coming weeks.
View all 30 community-submitted tasks that were resolved last week. For example, an issue where edits made by human translation administrators when marking pages for translation were incorrectly flagged as bot edits has now been fixed.
Updates for technical contributors
Lua modules can now use the visibleCategories property on a Titleobject to retrieve only the categories visible to readers. Previously, modules would retrieve all page categories, making it hard for users to distinguish visible ones from the hidden ones.
On web, on Wikipedia, ReadingLists will be renamed to Special:Saved. The old name will continue to work as an alias, so existing links will remain accessible. The change is being tested for compatibility with the Wikipedia apps’ reading list import and export functionality and is not expected to affect it. You can report any issues on Phabricator.
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)
Even though it was tagged incorrectly it was a clear request from a user to delete a page in their user-space so you could have just deleted as U1. KylieTastic (talk) 12:33, 18 November 2026 (UTC)
KylieTastic Us regular admins can't delete .JS files, you need to be an interface admin. Black Kite (talk) 12:40, 18 November 2026 (UTC)
I didn't have any delete option available to me on the page anywhere that one would be expected. Bearcat (talk) 14:31, 18 November 2026 (UTC)
Wikitext isn't rendered on js pages so deletion tags don't produce a box with a delete link but the interface still has it in a menu. PrimeHunter (talk) 15:29, 18 November 2026 (UTC)
Very odd. My delete option is in the 'More' menu on .js files that same as it is for other files. KylieTastic (talk) 15:50, 18 November 2026 (UTC)
I use MonoBook, so there is no dropdown menu - the "delete" thing is in a tab between "history" and "move", but I get it on other people's .js pages just the same as I do on other people's regular user pages. Clicking it gives the normal list of caveats, followed by the usual form to fill in, which finishes with Delete page. --Redrose64🌹 (talk) 20:08, 18 November 2026 (UTC)
In extremis, you can go to Special:Delete/User:Whoever/whatever.js or add ?action=delete or &action=delete (as appropriate) to the url. Used to regularly see people do beansy things that made getting at the links inconvenient. —Cryptic 04:58, 19 November 2026 (UTC)
Please provide more details when you report a problem. When I went to the article, I saw a red error message saying that the note called "electoral threshold" was not defined, which I'm assuming was the problem you were reporting. The error message was correct, since the note was defined outside of the excerpted section. I moved the note into the excerpted section, and things seem to be working fine now. If you were reporting a different error, please provide details. – Jonesey95 (talk) 19:21, 18 November 2026 (UTC)
That was exactly it. thanks LIrala (talk) 19:59, 18 November 2026 (UTC)
js in redlinked categories
The latest run of Special:WantedCategories again features redlinked categories on a user's js settings page, though it's not a misplaced deletion tag this time, but just regular run of the mill bad code.
Did you try to contact İmmortalance? They seem to be pretty active, especially on the Turkish Wikipedia. --Ahecht (TALK PAGE) 14:33, 19 November 2026 (UTC)
@Ahecht, @Bearcat, It was an issue caused by the coding structure. I've fixed it. They won't appear anymore. İmmortalance (talk) 15:12, 19 November 2026 (UTC)
@İmmortalance: A common method to avoid all issues with js pages being parsed as wikitext is wrapping the whole page in <nowiki>...</nowiki> on JavaScript comment lines like MediaWiki:Gadget-morebits.js. PrimeHunter (talk) 16:25, 19 November 2026 (UTC)
I wanted to find all the Community Wishlist wishes I've voted for, so I searched for insource:"username nardog" OR insource:"userid 905504" prefix:Community Wishlist/W, but got no results. Of course I can use regex, but that wouldn't scale for thousands of pages. Is there no way to perform a search combining insource: and OR? Nardog (talk) 21:27, 19 November 2026 (UTC)
prefix: must be at the end. I think your first search is interpreted as the prefix being "Community Wishlist/W" insource:"username nardog". It's an annoying and unintuitive limitation that the prefix must be last in searches. I think the idea is that it can search for page names which happen to contain quotation marks and search syntax but how often is that actually wanted? I have long thought about making a Phabricator request which allows the prefix to be delimited by quotation marks like other search parameters. If the developers don't want to break existing rarely used functionality then a special syntax will be required, e.g. a new parameter prefixq: for the normal behaviour: The first word or a quoted string. PrimeHunter (talk) 08:55, 20 November 2026 (UTC)
It should come with a warning of some sort at least, or it should print out the actual prefix it searched for. Interestingly, insource:// prefix: does seem to be optimized, it doesn't take many seconds to get the result as with the regex search alone. Ponor (talk) 11:34, 20 November 2026 (UTC)
There are only 2,913 pages with the prefix, which won't take long to search even with an inefficient regex. Certes (talk) 17:57, 20 November 2026 (UTC)
Yeah, but normally something like insource:/regex/ prefix: would mean: search for regex (10 seconds max), then filter out by prefix: – it goes from left to right. Ponor (talk) 18:06, 20 November 2026 (UTC)
Inconsistent list of IPs associated with TAs
I don't know if this is a bug or if there's just something I'm not understanding about how this works. I have TAIV, and if I look at the User contributions page for a TA, at the top of the page it lists "Temporary accounts from all associated IPs". I would expect that if I click on any of those listed TAs, I will see the same list of TAs. However this is not always the case. For example, Special:Contributions/~2026-59331-22 shows four TAs. If I click on any of the first 3, I see the same list of 4. However, if I click on the last one, I see a list of 6, the original four plus two more. If this is not a bug, can someone explain this behavior? CodeTalker (talk) 21:36, 19 November 2026 (UTC)
I'm not a TAIV user but I guess that the tool only shows direct connections. Suppose 2026~1 and 2026~2 both use 1.2.3.4, and 2026~2 and 2026~3 both use 5.6.7.8. Then 2026~2 is associated with both 2026~1 and 2026~3, but 2026~1 and 2026~3 are not associated with each other and only list 2026~2. Certes (talk) 22:25, 19 November 2026 (UTC)
Soft clear
I made a template, {{Soft clear}}, that can fix some cases of paragraphs being squished by floating images or tables. It's a bit like a {{Clear}} conditional on how much horizontal space is available.
You can see it in action by resizing your browser window on:
It's a neat technique. We use it in MediaWiki too to clear some elements of the page if they would be squished below a certain width. For example, the reply box I'm typing in right now (code here) – if you try to reply to my comment, it will normally show next to the floated image, but it will clear below it if your browser window is narrow enough. Matma Rextalk 16:14, 20 November 2026 (UTC)
Javascript errors
Is anyone kindly able to advise how to fix the cause of the JavaScript errors I pasted at:
I get them on Wikisource, but not Wikipedia or other projects.
I use Firefox and restarting my machine, changing accounts or disabling ad-blockers does not help. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits; 13:19, 20 November 2026 (UTC)
The references to content.js makes me think it's a Firefox extension that's doing it, but you said you disabled ad blockers. Try disabling all your extensions and seeing if that fixes it. If that's not the problem, and if by "changing accounts" you mean using a different Firefox profile, then it would have to be an antivirus software or VPN that is injecting the script-src 'none'. --Ahecht (TALK PAGE) 14:59, 20 November 2026 (UTC)
Thanks.
By "changing accounts", I meant logging in with an alternative Wikimedia account. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits; 15:10, 20 November 2026 (UTC)
This section is resolved and can be archived. If you disagree, replace this template with your comment. Found the cause - an extension. Thank you. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits; 15:21, 20 November 2026 (UTC)
Upcoming Suggestion Mode discoverability and read-mode test
The welcome dialogue that will greet first-time editors on articles with available suggestions during the test.
Hi all! The Editing team is continuing work on Suggestion Mode, and we wanted to let you know about an upcoming experiment we're planning.
Background
As a reminder, we developed Suggestion Mode in response to the finding that a large number of readers have been clicking the edit button because they're curious to try editing but then closing the editor when they find no compelling edits to make. Suggestion Mode identifies opportunities for them to improve the article, such as removing a duplicate link, and then guides them through the process of making the edit. We're seeing signs that this can both spur useful contributions and give newcomers a positive first edit experience that encourages them to return and grow into the experienced editors of the future. It's currently live as a beta feature, so you can try it out for yourself! Just go to your beta settings to enable it and then edit using the VisualEditor. You can see the suggestion types currently available here by visiting Special:EditChecks (they are configurable by admins). We are working on additional ones and also hope you all will add your own using the TextMatch feature.
Separately, we are aware of the sentiment expressed in places like this wish to more actively invite readers to try editing.
Experiment results
In May and June, we ran an A/B test at 15 wikis in which we turned on Suggestion Mode for half of newcomers. Among users who engaged with suggestions, we found positive indicators on metrics like edit completion rate and retention. However, we found that only roughly a quarter of the test group clicked/tapped to view a suggestion on articles where one was available. Our working hypothesis is that this means that we have a discoverability problem.
Discoverability test
Icons in read mode indicating that a suggested edit is available
To test this hypothesis, we'd like to try out a user experience that makes suggestions more prominent to people who are logged in on mobile web and desktop and have published up to 100 edits, in two ways:
Greeting them with a pop-up dialogue featuring Baby Globe if they are editing an article which has any suggestions. The plan is for this onboarding experience to only appear the first time someone begins an edit session where at least one suggestion is available. In subsequent edit sessions, the onboarding experience will not be shown, even if edit suggestions are available.
Showing the blue lightbulb icon next to the pencil edit icon in articles to indicate to people who might be curious to try editing that there is a suggestion available for that article.
The experiment is planned to start on Thursday, November 26th and run for 4-6 weeks. While the experiment is active, 50% of logged-in newcomers (≤100 cumulative edits) will see the Suggestion Mode onboarding experience the first time they tap edit and the other 50% will see the normal Suggestion Mode experience.
You can test out this user experience via this prototype (in English). Open it on a mobile device and tap edit. To see the first-timer pop-up, tap on your user icon to open the mock settings and enable "First time using suggestion mode" in the "Suggestions" tab.
Following this test, we'll analyze the results to see whether this user experience leads to an overall increase in the same metrics we tracked for the experiment earlier this year. That will then inform our next steps.
As always, we're eager to know what you think! Thanks for your ongoing collaboration on Suggestion Mode!
Cheers, Sdkb‑WMFtalk 17:09, 20 November 2026 (UTC)