Wikipedia:Village pump (technical)

Whenever I attempt to save my settings (both on mobile and laptop) it instantly resets as soon as I leave the settings page, regardless of whether I have clicked save. Has anyone else experienced this? The main issue for me is the email settings and I am considering just removing my email address so I am not constantly receiving emails, however it does mean that if I forgot my password I will be locked out of my account. Any help would be greatly appreciated. Longhorncowfish (talk) 20:32, 1 July 2024 (UTC)Reply

Try accessing Special:Preferences and saving the preferences with JavaScript off (google how to turn it off, it depends on browser). Nardog (talk) 02:45, 2 July 2024 (UTC)Reply

Or try another browser or device. PrimeHunter (talk) 03:23, 2 July 2024 (UTC)Reply

I have tried on both iPhone and laptop and it doesn’t work :( Longhorncowfish (talk) 01:59, 3 July 2024 (UTC)Reply

I cannot do that on my current device, but I will try when possible Longhorncowfish (talk) 02:00, 3 July 2024 (UTC)Reply

This is supposed to happen at Special:Preferences#mw-prefsection-personal in desktop:

1. The Save button is grey
2. Click once in the box at "Email me when a page or a file on my watchlist is changed"
3. The box changes state between empty white and blue with checkmark.
4. The Save button is now blue
5. Click the Save button
6. The Save button is now grey
7. "Email me when a page or a file on my watchlist is changed" still has the new setting
8. If you leave preferences and come back then it still has the new setting

If it's different for you then at which step? PrimeHunter (talk) 10:20, 3 July 2024 (UTC)Reply

The button never goes gray. If I click it nothing happens Longhorncowfish (talk) 03:35, 5 July 2024 (UTC)Reply

Not even a page reload? Nardog (talk) 06:16, 5 July 2024 (UTC)Reply

@Longhorncowfish: What is your skin at Special:Preferences#mw-prefsection-rendering? What is your browser and operating system on the laptop? If you change a setting so the Save button becomes blue then does it become lighter blue with a hover-text like "Save preferences [Alt+Shift+s]" when you hover over it? Does it turn grey if you use the keyboard shortcut? Alt+Shift may be different for you, see Help:Keyboard shortcuts#Using access keys. Can you save by pressing Tab ↹ until the Save button is marked and then ↵ Enter? PrimeHunter (talk) 20:25, 7 July 2024 (UTC)Reply

 

The page preview, which for some reason links to a different article

 

The article itself, which shows that the page previewer is jacked up

I was working on an article, Downtown One (which is not a redirect), when I realized that the article preview links to a completely different article, which is List of tallest buildings in Albania. A redirect from the former to the latter did exist at one point in time, but was deleted in 2023. The bug should be visible to others, if it's not just let me know, I can post an image up. This is a relatively serious bug aswell, because it basically removes the ability to visit that page, effectively eliminating the purpose of Wikipedia. I've never seen this before, so I thought I'd let yall know. (Also I attempted to report it over at Phabricator, but for some reason the ver. email link never sent). At least one person over at WP:TEAHOUSE is completely clueless as to why that happens, and honestly so am I. Thanks :) Sir MemeGod ._. (talk - contribs - created articles) 03:32, 6 July 2024 (UTC)Reply

I failed to reproduce the problem. Graeme Bartlett (talk) 05:17, 6 July 2024 (UTC)Reply

It just fixed itself. That is the weirdest thing. Sir MemeGod ._. (talk - contribs - created articles) 05:20, 6 July 2024 (UTC)Reply

  Sir MemeGod ._. (talk - contribs - created articles) 05:23, 6 July 2024 (UTC)Reply

The redirect existed for 15 hours on 7 August 2023. Page Previews uses caching. I guess the cache was never updated after the deletion. I don't know whether this is normal for deleted redirects or pages. Page Previews doesn't activate on red links so it wouldn't normally affect users but it did when you recreated the page with other content. The cache was apparently updated between your first and second post, meaning between one and three hours after page creation. There are reasons for caching but 11 months is too much so I would call this a bug. PrimeHunter (talk) 10:33, 6 July 2024 (UTC)Reply

Page previews don't get actively purged on delete/revert/move/etc, only on edit. And then they still are cached for 24 hours (not sure what the exact value is). This is a known issue (or rather two of them). So what happened is that when you recreated the article, it used the OLD information (as it was still somewhere in the database), that got cached, edits were made causing references to update in the databases, and then 24 hours later the cache expired and it used the new information from the edits. —TheDJ (talk • contribs) 11:03, 10 July 2024 (UTC)Reply

So, say someone creates a vandalistic page containing an objectionable image. The page gets deleted as G3. Later, someone creates a legitimate page at - or moves an existing page to - the same title. Is the preview going to show whatever picture that was previously on the vandalistic page? That could cause some surprises. Home Lander (talk) 20:00, 10 July 2024 (UTC)Reply

If I click on a link to WP:ANI#Pizza (but not Mars#Pizza), a popup appears in the upper-right hand corner of the browser satating the obvious, This topic could not be found. It might have been deleted, moved or renamed. [sic] Which preference or gadget has enabled this? I can't find anything that describes such in my preferences, and I don't see anything documented at WP:ANCHOR, Help:Section#Section linking, or MOS:SECTIONLINKS. Anybody know what's causing this? — Fourthords | =Λ= | 04:49, 6 July 2024 (UTC)Reply

mw:Extension:DiscussionTools. Just curious, why "[sic]"? Nardog (talk) 04:56, 6 July 2024 (UTC)Reply

I don't see that specific popup listed at that link, but I'll take your word for it. As it's both new and woefully superfluous, is that something still being experimented upon (and we can wait it out), or does it need to be fixed at the project or individual-editor level? (I just used {{sic}} to denote that the missing serial comma was original to the popup, and not a mistake on my part.) — Fourthords | =Λ= | 10:28, 6 July 2024 (UTC)Reply

It's a MediaWiki feature that has existed for several weeks. The HTML is

<div class="mw-notification-area-overlay">
  <div class="mw-notification-area mw-notification-area-layout" id="mw-notification-area" style="">
    <div role="status" class="mw-notification mw-notification-noautohide mw-notification-type-warn mw-notification-visible">
      <div class="mw-notification-content">This topic could not be found. It might have been deleted, moved or renamed.</div>
    </div>
  </div>
</div>

and it's right at the end of the HTML source that is served to your browser. The same <div class="mw-notification-area-overlay">...</div> is used to contain the "Your edit was published." message that you get when you save an edit, also some other messages. --Redrose64 🌹 (talk) 14:09, 6 July 2024 (UTC)Reply

I don't know how to remove only this message. This in your CSS removes all mw-notification-area-overlay:

.mw-notification-area-overlay {display:none;}

This in your common JavaScript only works if it runs after the popup has appeared but it normally runs before:

$('.mw-notification-area-overlay:contains("This topic could not be found")').hide()

PrimeHunter (talk) 14:21, 6 July 2024 (UTC)Reply

I've found two more messages that go in the same area - '"(page name)" and its talk page have been added to your watchlist permanently.' and '"(page name)" and its talk page have been removed from your watchlist.', so that makes four, although there may be others. @Fourthords: I've worked out how to hide the "This topic could not be found. It might have been deleted, moved or renamed.", leaving the other three visible:

#mw-notification-area:has(div.mw-notification-noautohide.mw-notification-type-warn) {
  display: none;
}

which goes in your CSS. The selector might be overspecific. --Redrose64 🌹 (talk) 16:12, 6 July 2024 (UTC)Reply

Oh gosh, I hadn't mean to attract so much attention and assistance; I was just expecting a point in the correct direction. Thanks so much! — Fourthords | =Λ= | 18:09, 6 July 2024 (UTC)Reply

A problem with all these approaches is that it would also hide a notification which does point to an archived section (e.g. WP:VPT#Heading markup changes). Nardog (talk) 04:09, 7 July 2024 (UTC)Reply

The two messages have the same classes and id's and the unwanted message doesn't have anything unique apart from the actual text which cannot be selected with CSS, but only the wanted message has <p>. We can use this to hide both and then unhide the wanted:

#mw-notification-area:has(div.mw-notification-noautohide.mw-notification-type-warn) {
  display: none;
}
#mw-notification-area:has(div.mw-notification-noautohide.mw-notification-type-warn p) {
  display: inline;
}

PrimeHunter (talk) 09:32, 7 July 2024 (UTC)Reply

@PrimeHunter: Which two messages have the same classes and id's? --Redrose64 🌹 (talk) 18:26, 7 July 2024 (UTC)Reply

The "This topic could not be found..." popups on WP:ANI#Pizza and WP:VPT#Heading markup changes. PrimeHunter (talk) 19:05, 7 July 2024 (UTC)Reply

When I do not login, the search box is not visible (on my HP laptop running Windows 11, using Firefox or Brave) unless I hit ctrl and the minus key at least three times. I wouldn't be surprised if there aren't potential users who have come to Wikipedia and left after not finding a way to search. Can't this set-up be changed? (When I'm logged in, the issue does not occur.) Kdammers (talk) 03:48, 7 July 2024 (UTC)Reply

If I zoom in 175% it turns into a magnifying glass symbol, which I can then click to display the searchbox. – 2804:F1...04:60E (talk) 04:06, 7 July 2024 (UTC)Reply

@Kdammers: See Wikipedia:Village pump (technical)/Archive 213#Search box and Wikipedia:Village pump (technical)/Archive 213#Bugs persisting after last week. --Redrose64 🌹 (talk) 18:23, 7 July 2024 (UTC)Reply

POTY desperately needs new volunteers who can do the things required to run the competition. With the current state of the committee, it is likely that there will be no POTY this year, as the main member who ran scripts for the competition has burned-out from doing wikipedia tasks and isn't up for it. Others on the committee are also missing in action.

Check out the Discussions here commons:Commons_talk:Picture_of_the_Year and here User_talk:Jimbo_Wales#Wikimedia_Commons_POTY. @Tacsipacsi has helped out with fixing some issues with code.

Volunteers familiar with Rust, JavaScript, wikitext and SQL are needed. Links to scripts: [1] and [2]. Please help out if you can.•Shawnqual• 📚 • 💭 23:22, 7 July 2024 (UTC)Reply

On each level of the WP:Vital articles pages, the random article buttons somehow stopped working. I tried this on my laptop and phone, and it doesn't work. What happens is when I press the button, I get an error that says the tool is down. I was wondering what caused this and how I can fix it so that it works again. Interstellarity (talk) 13:40, 8 July 2024 (UTC)Reply

It looks like that uses the RandomInCategory tool, which is maintained by Ahecht. --rchard2scout (talk) 15:44, 8 July 2024 (UTC)Reply

@Interstellarity, Rchard2scout: Thanks for the ping. I'll look into that later when I have access to my home computer. --Ahecht (TALK
PAGE) 16:06, 8 July 2024 (UTC)Reply

@Interstellarity, Rchard2scout All set. The webservice just needed a kick, and had a little trouble starting the first time -- probably something to do with the gridengine shutdown. --Ahecht (TALK
PAGE) 18:03, 8 July 2024 (UTC)Reply

@Ahecht: Thank you for fixing it. Interstellarity (talk) 00:43, 9 July 2024 (UTC)Reply

MediaWiki message delivery 21:29, 8 July 2024 (UTC)Reply

When you use the same reference more than once, the individual instances get assigned tags a, b, c, etc. Once you get past 26, it wraps around to aa, ab, ac and so on up to az, then picks up with ba, bb, and so on. As part of a tool I'm writing, I need to be able to generate these. My first thought was "its just base 26 using "a" through "z" to represent 0 through 25 in each column". But its not (he says after beating his head against the wall writing some python code to do base 26 conversion). If it were, then after "z" would come "ba" for "1 in the 26's column plus 0 in the 1's column". So what is this sequence? Is there some standard name for it? RoySmith (talk) 15:49, 9 July 2024 (UTC)Reply

@RoySmith See Bijective numeration#The bijective base-26 system. --Ahecht (TALK
PAGE) 15:57, 9 July 2024 (UTC)Reply

Here is some quick python code to do the conversion:

def bijectiveHexavigesimal(n):
  outStr = ''
  while n != 0:
    outStr = chr((n - 1) % 26 + 97) + outStr
    n = (n - 1) / 26
  return outStr

--Ahecht (TALK
PAGE) 16:10, 9 July 2024 (UTC)Reply

(for the archives: this takes 1-based numbers, and the "/" should be "//" for Python-3) — Preceding unsigned comment added by RoySmith (talk • contribs) 17:36, 9 July 2024 (UTC)Reply

I'm curious, why do you want to generate reference numbers? Legoktm (talk) 16:08, 9 July 2024 (UTC)Reply

@Ahecht Cool, thanks!

@Legoktm I'm not sure exactly where this is going, but I'm working on something to make it easier to do reference spot-checks for GA and FA reviews. So you'd be able to say something like "pick 10% of the statements in the article and show me what they're sourced to" Using the current version of Oceanic whitetip shark), it might tell you that It is eaten fresh, smoked, dried, and salted and its skin made into leather is cited to reference 6-k. I can dig out of the generated HTML <sup id="cite_ref-FAO_6-10"> but I don't want to show that gibberish to the user.

This has been a frustrating project so far. It's been a series of, "Oh, all I need to do is..." false starts, foiled by the reality of just how perverse everything related to wiki text is. Not to mention how we don't have one uniform referencing style I can target. RoySmith (talk) 16:33, 9 July 2024 (UTC)Reply

I hope that you stick with it. A tool like that would be very helpful to those of who do spot-checks and might create an easier learning curve for new reviewers. Firefangledfeathers (talk / contribs) 19:19, 9 July 2024 (UTC)Reply

You would think that it's some clever algorithm, but actually, there is just a big list at MediaWiki:Cite references link many format backlink labels. Matma Rex talk 19:12, 9 July 2024 (UTC)Reply

And which article was it that required more than 702 repeated uses of a reference, and pushed MediaWiki to use three-character ids? Or was it just paranoia? -- Verbarson  ^talk_edits 19:18, 9 July 2024 (UTC)Reply

This edit from 2010: [3] refers to List of allied military operations of the Vietnam War, which is today mercifully a list of lists, but the 2010 version: [4] re-used a reference a cool 1037 times. Matma Rex talk 19:25, 9 July 2024 (UTC)Reply

Oh, my RoySmith (talk) 20:39, 9 July 2024 (UTC)Reply

I see you and raise you List of marine bony fishes of South Africa, with 1,378. I found it the same way I found the previous record holder. Graham87 (talk) 03:23, 10 July 2024 (UTC)Reply

Which was right on the limit. Via search/replace all I thought it was one less than the limit (because there were 1,379 instances of the ref name), but the other one turns out to be because of list-defined references. I'd added more ref labels to the MediaWiki page before realising this; if someone really wants to revert my edit there, be my guest, but I can't think of a good reason to do so at this point. Graham87 (talk) 03:45, 10 July 2024 (UTC)Reply

What actually happens when someone adds more repeated refs than the list provides for? -- Verbarson  ^talk_edits 07:35, 10 July 2024 (UTC)Reply

See the end of User:Graham87/sandbox30, which apparently answers your question; in this case it says "[[#cite_ref-test_1-2054|]]" before the ref text, which is "Test ref". I created this file by adding the first line with the ref declared, then writing the next line with a named ref, copying it to the clipboard and pasting it, copying and pasting the resulting two lines, then the resulting four, eight, sixteen, etc. ... lines, all the powers of two. Graham87 (talk) 09:00, 10 July 2024 (UTC)Reply

I recently left a standard WP:ARBPIA alert on User talk:EliasAntonakos. Apparently I didn't get it right (I'm a bit rusty at the moment; I am mostly on wiki-break), as no messages after that shows up on their page. (see talk-history for futher messages) What did I get wrong? Huldra (talk) 21:10, 9 July 2024 (UTC)Reply

There's an unclosed <!-- from the original notice causing everything after it to be hidden, need to close it with -->. Indagate (talk) 21:16, 9 July 2024 (UTC)Reply

User:Indagate; thanks! It worked! Huldra (talk) 21:20, 9 July 2024 (UTC)Reply

@Huldra: How did you make the original post? You were supposed to write {{subst:alert/first|a-i}} per Template:Contentious topics/alert/first#Usage, but that should automatically include the closing --> with no way to delete it in the same post. Did you instead try to copy-paste the message from another page? PrimeHunter (talk) 21:27, 9 July 2024 (UTC)Reply

@PrimeHunter: Indeed I did (copy-paste the message, that is). As I said above; I'm a bit rusty at the moment (mostly on wiki-break until the end of the year), Huldra (talk) 21:34, 9 July 2024 (UTC)Reply

 

Hey, this is a continuation of the topic "Dark mode for logged-out users coming soon", specifically about desktop (the Vector 2022 skin).

In that previous message, we announced that dark mode on desktop would be rolled out in one step, for both logged-in and logged-out users, in the week of July 15 (that is, next week). However, we'd be more comfortable to enable it for logged-in users first. Articles here on English Wikipedia look very good in dark mode, and again, thanks to everyone who is contributing to it!

We are going to enable dark mode on desktop just for logged-in users this week. If everything goes well (it has been going very well so far!) we will enable it on desktop for logged-out users next week as we previously announced. It's gonna be exciting :D Thanks! SGrabarczuk (WMF) (talk) 01:35, 10 July 2024 (UTC)Reply

@SGrabarczuk (WMF): What do you mean by "We are going to"? I thought it was enabled for logged-in users already? Nardog (talk) 06:29, 10 July 2024 (UTC)Reply

It was only Logged in users with the beta option enabled before. —TheDJ (talk • contribs) 07:31, 10 July 2024 (UTC)Reply

Oh. Does it mean "Accessibility for Reading" will no longer be a beta feature, or just the dark mode? Nardog (talk) 07:38, 10 July 2024 (UTC)Reply

Yes, exactly. SGrabarczuk (WMF) (talk) 11:05, 10 July 2024 (UTC)Reply

@SGrabarczuk (WMF): Yes, what? That was not a polar question. Nardog (talk) 11:10, 10 July 2024 (UTC)Reply

Oh, sorry, I wanted to give a quick answer and misread :D Dark mode will no longer be a beta feature. Font size control will continue to be a beta feature. SGrabarczuk (WMF) (talk) 11:39, 10 July 2024 (UTC)Reply

Correction: The font size control is already available by default. The beta feature will disappear from the list because after this rollout, all options will be available for everyone. SGrabarczuk (WMF) (talk) 18:31, 10 July 2024 (UTC)Reply

What happens to people (like me) who don't use Vector? Will dark mode still be available in MonoBook? — Preceding unsigned comment added by Nigel Ish (talk • contribs) 19:04, 10 July 2024 (UTC)Reply

Dark mode is supported only in Minerva and Vector 2022. Izno (talk) 21:30, 10 July 2024 (UTC)Reply

So the existing dark mode (that does work in MonoBook) will stop working. Wonderful.Nigel Ish (talk) 21:43, 10 July 2024 (UTC)Reply

If by "existing dark mode that does work in Monobook" you mean the gadget? No, that will continue to function. Izno (talk) 21:45, 10 July 2024 (UTC)Reply

Eww, this one caught me by surprise... The contrast doesn't seem quite right at the moment. I don't think "dark mode" should be black, it should be off black for the best ease on the eyes. Hopefully the WMF will get these things right in due course.  — Amakuru (talk) 21:36, 10 July 2024 (UTC)Reply

It's flicking black/white off-and-on for me. Page loads in dark & then seconds later turns white. The next page loads in white & seconds later flicks to black. Plus the diffs aren't visible in black. Instant migraine for me. Safari 16.6. Victoria (tk) 21:49, 10 July 2024 (UTC)Reply

Same. On my end, it was enabled by default and I had to go into preferences to enable the toggle just to turn it off in the interface. Now it flickers every time the page loads. Viriditas (talk) 22:10, 10 July 2024 (UTC)Reply

I turned off the toggle in preferences, emptied my cached, restarted the machine. Still happening. Now the white pages render with the dark colors before turning completely black after about 5 seconds. I took screen shots. It seems to take 3 to 5 seconds to flick from white to black & then back again. Victoria (tk) 22:37, 10 July 2024 (UTC)Reply

Yeah, one wonders if this is causing seizures. "For 3% of people with epilepsy, exposure to flashing lights at certain intensities or to certain visual patterns can trigger seizures." Viriditas (talk) 22:50, 10 July 2024 (UTC)Reply

This is true which is exactly why I'm unable to upload the screenshots. This is very very bad. Victoria (tk) 22:53, 10 July 2024 (UTC)Reply

Makes me wonder why nobody else is reporting it or is the least bit concerned. I've got a brand new computer as well. Viriditas (talk) 22:57, 10 July 2024 (UTC)Reply

I switched to Vector legacy in preferences as a workaround. Viriditas (talk) 23:00, 10 July 2024 (UTC)Reply

Hey there! I've added this to our FAQ. If you are seeing a flick from white to black, you have enabled the gadget AND have attempted to try out the new feature (possibly via preferences when it was in beta or via the new preference that now appears in the preferences page).

The number of people using the gadget is quite low compared to the number of viewers so I am not concerned that this is impacting a large amount of people. Jon (WMF) (talk) 23:01, 10 July 2024 (UTC)Reply

Hi Jon (WMF), please re-read my message. I disabled the gadget, doublechecked that it's gone, emptied my cache, restarted my machine. It's still happening. I will have to log out to override this. If you would like to see screen shots taken with the gadget disabled I'm happy to send them on, but you'll have to contact me. Victoria (tk) 23:21, 10 July 2024 (UTC)Reply

That's what I initially thought, but the gadgets were all unchecked when it went live. Now, I get dark mode by default unless I check the preferences. I'm in Vector legacy to avoid all of it, because I can't fix it. Viriditas (talk) 23:05, 10 July 2024 (UTC)Reply

Note, the dark-mode-toggle-pagestyles gadget is hidden on user preferences so it is possible you still have that enabled (it doesn't show up in preferences)

A few questions which will help us get to the bottom of this:

• In legacy Vector are you seeing the dark mode gadget toggle in the top right?
• If you enable Vector 2022, do you see the message "You're using a dark mode gadget". If yes, what happens when you click it and the page reloads?

Jon (WMF) (talk) 23:17, 10 July 2024 (UTC)Reply

In legacy Vector are you seeing the dark mode gadget toggle in the top right?

No.

If you enable Vector 2022, do you see the message "You're using a dark mode gadget".

No, unless I'm missing it. How do I fix dark-mode-toggle-pagestyles, if that is the problem? Viriditas (talk) 23:26, 10 July 2024 (UTC)Reply

Okay, I found it. There are two toggles for dark mode in preferences >> gadgets. One under "appearance" and then another one all the way under "utility". Both have to be turned off. Mine was still turned on under utility. The flickering only stops when they are both turned off. To find the control for dark/light mode now, one has to go to preferences >> appearance >> color. Color?? Seriously? In the meantime, Jon (WMF), I sent an email with screenshots, but it's now irrelevant. Victoria (tk) 23:54, 10 July 2024 (UTC)Reply

Yeah, that's in "gadgets", and doesn't work for me. I have both off, and I'm still in dark mode. If I switch them on, and then turn off dark mode, I get the flickering. If I switch them off, I'm in permanent dark mode. Viriditas (talk) 00:12, 11 July 2024 (UTC)Reply

Oh, Victoria is right, that worked. I had to change appearance > color to "light". Problem solved. Viriditas (talk) 00:20, 11 July 2024 (UTC)Reply

Hmm really not a fan of this new default setting. Has this even been tested by a broad group of people including casual users (not just people heavily involved in Wikipedia?

The "dark mode" is ironically way too bright because this is a text-heavy site. So, what you get now is a mass of white text, not a dark page. It almost seems *more* white. The drastic differences between the colors make it difficult to skim. (I don't mind it so much when I'm reading closely, but skimming is important, too.)

Also - this is a little pet peeve, but important for research. The color of already-clicked links doesn't change in info boxes (sorry I don't know the exact term but in a bio page, it would be the box on the top right with basic info like DOB, city, parents, etc.). This isn't a browser issue because it works in Vector legacy. Jim0101 (talk) 04:17, 11 July 2024 (UTC)Reply

@Jim0101 "new default setting" The default will remain light mode, the only thing changing is that you get an OPTION to set dark mode... —TheDJ (talk • contribs) 12:20, 11 July 2024 (UTC)Reply

K well it switched to dark mode without me choosing that option. So that's naturally why I assumed it was the default setting when it did in fact default to that for me. Jim0101 (talk) 12:23, 11 July 2024 (UTC)Reply

I am using a script which highlights different type of pages in different colors (sorry do not remember the name), this gives me as default blue on black, and this is not readable. I generally like the dark background, but here I had to switch back (using the appearance tab in the preferences). I can not switch off the script because I work a lot with category deletion, and categories need to be tagged.--Ymblanter (talk) 05:59, 11 July 2024 (UTC)Reply

User:Anomie/linkclassifier? Nardog (talk) 06:25, 11 July 2024 (UTC)Reply

Yes, I think so. Ymblanter (talk) 06:31, 11 July 2024 (UTC)Reply

Yes, re contrast and readability I concur. I used it for a bit last night and my eyes were hurting by the end with some of the text impossible to read. Per Ymblanter above, I think this needs to go out to a proper group of test readers and full feedback taken on board before we roll it out as a default.  — Amakuru (talk) 08:00, 11 July 2024 (UTC)Reply

The linkclassifier script's colors are easy to customize if you know CSS. The default User:Anomie/linkclassifier.css isn't even required to be used. If someone wants to suggest a full set of colors for dark mode, that could be useful to incorporate in the default. Anomie⚔ 11:40, 11 July 2024 (UTC)Reply

Has anyone raised an issue with new notifications background going from white to dark background upon read? The text is unreadable. – robertsky (talk) 06:37, 11 July 2024 (UTC)Reply

Thanks for your report @Robertsky! I'm wondering if you could give a bit more detail on where you're seeing this? Are you talking about notifications on the Special:Notifications page? Or within the menu in the top right? If possible, a screenshot would be really helpful as well so we can identify where the issues is. Thanks again. OVasileva (WMF) (talk) 11:25, 11 July 2024 (UTC)Reply

I've noticed that If you open "Notices" and then have new messages "from other wikis", that block in your notices shows a baby blue highlight color for 2 to 3 seconds or something, which is not yet dark mode compatible. —TheDJ (talk • contribs) 12:09, 11 July 2024 (UTC)Reply

Thanks for giving Wikipedia a dark mode option! The settings page says Experimental version, high likelihood of experiencing issues--am i being helpful if i say i think i've found one?

^{Do we have (or should we have) a central thread where all of the discussions about the launch of dark mode should be in one place?}

i've visited maybe a half dozen pages where dark mode seems to work, but the Willys 77 page still won't turn to the dark side, even after i:

• reload the page,
• close and reopen the tab,
• open a new tab and type the URL into the address bar,
• create a new link to that page (as in this post) and use that to open the page,
• change settings back and forth a few times,
• or retry the methods listed here, but in a different order.

Additionally, Wikipedia:Help desk is mostly dark. i'm not sure if it's the same issue mentioned here, but this part:

Welcome...
(Am I in the right place?)...
For other types of questions...
Do not provide your email...
New editors may prefer the Teahouse...
[Ask a question]
show/hide Wikipedia help pages

this part stays white.

Wishing everyone safe, happy, productive editing.

--173.67.42.107 (talk) 22:23, 10 July 2024 (UTC)Reply

Willys 77 turned black. --173.67.42.107 (talk) 23:13, 10 July 2024 (UTC)Reply

Hello, thank you for reaching out here! I'm glad to see that the article turned black. It always takes a few days for new changes to be propagated across all pages because of caching. When we started running banners inviting logged-out users to switch to dark mode, the cache of just a few percent of the articles wasn't refreshed.

When it comes to the Help desk, I'm sure English Wikipedians will soon fix it. It is challenging, though. There are so many pages formatted with the assumption that the only mode is light, and there's a lot of special formatting on non-article pages. But reports like yours help technical editors prioritize their work.

Thanks again, for pointing at these issues, for your patience (so many steps to solve the problem of the persisting light mode), and kind words! SGrabarczuk (WMF) (talk) 00:32, 11 July 2024 (UTC)Reply

I have fixed all of the dark mode Linter issues at Wikipedia:Help desk except for the ones caused by {{Collapse top}}, which is fully protected. – Jonesey95 (talk) 14:28, 11 July 2024 (UTC)Reply

The default foreground color for text is way too bright/white and more than a few page elements on certain pages are as bright as light mode. Overall, it does not seem like an improvement on the old beta dark mode. I'd simply disable it and stick with the old beta dark mode for now, but if I do that, there's a white flash at the start of every page load and page refresh, which defeats the purpose of using a dark mode.

Here's several screenshots to show before vs. after.

Also, is there documentation somewhere describing the changes to the CSS? .client-dark-mode stopped working. Thanks. Daniel Quinlan (talk) 07:40, 11 July 2024 (UTC)Reply

Not having used the beta, the new version looks superior. A wp:village shrine should be erected to mark the occasion of implementation.

Though, the contrast issue may be a thing. Fiddling around with my monitor-settings, it feels like the default could be reduced quite significantly without other issues. JackTheSecond (talk) 09:10, 11 July 2024 (UTC)Reply

Dark mode turned on for me yesterday evening, and I found it very difficult to read, especially the watchlist page, where I had great difficulty seeing which changed pages I had already looked at. I managed to turn dark mode off, except that each page loads in dark mode, and I have to wait several seconds until it switches to light mode. At least dark mode is not popping up this morning. Donald Albury 12:07, 11 July 2024 (UTC)Reply

WRT to documentation, See mediawikiwiki:Recommendations_for_night_mode_compatibility_on_Wikimedia_wikis. —TheDJ (talk • contribs) 12:14, 11 July 2024 (UTC)Reply

The font size in footnote popups seems to have suddenly changed to dramatically larger font size than previously, and now appears to be significantly larger than body copy in my skin (old-school MonoBook + some personal CSS modifications).

Because the width of footnote popup boxes hasn't changed, much less text now fits on each line, which combined with the bloated font size makes the footnotes now take up like 1.5 or 2x more space than previously. I find the new popups both less legible per se, and also much more disruptive because they cover more of the content below. Footnotes which try to include more detailed material end up fitting worse inside the available popup space.

Was this change discussed anywhere? In my opinion it should be reverted. There is no good reason for footnote popups to ever have a larger font size than body copy. Ideally they would have a slightly smaller font size, but the same size is also okay. (I can't even remember precisely what they were like before.)

–jacobolus (t) 05:39, 10 July 2024 (UTC)Reply

It's MediaWiki talk:Gadget-ReferenceTooltips.js#Update request 9 July 2024, and ‎JWBTH is on it. Nardog (talk) 06:27, 10 July 2024 (UTC)Reply

Thanks! –jacobolus (t) 06:52, 10 July 2024 (UTC)Reply

For anybody interested – please join the discussion at MediaWiki talk:Gadget-ReferenceTooltips.js#Update request 9 July 2024 as to how should the tooltip font size correlate with body font size across different skins and text size settings, and whether we should use #mw-teleport-target as the wrapper for the tooltip. Jack who built the house (talk) 07:29, 10 July 2024 (UTC)Reply

I found a couple of pages where the page previews isn't working properly: E. O. Wilson and Fiji. I'm guessing that there is some wikitext element (bracket etc) that isn't closed properly, but can't see anything.  —  Jts1882 | talk  09:19, 10 July 2024 (UTC)Reply

They look fine in mw:Page Previews. The problems are in Wikipedia:Tools/Navigation popups. PrimeHunter (talk) 09:43, 10 July 2024 (UTC)Reply

Examining old revisions of E. O. Wilson, Popups failed on [5] which inserted <!-- Work in Progress Lede --> in January 2023 and made Popups only display }}. Popups tries to identify and display text from the first paragraph excluding an infobox and various stuff at the top of pages. If something makes Popups think it has reached the first "real" paragraph then it displays that, sometimes producing an empty display because Popups ignores templates. I don't know why this displayed }} instead of empty when the brackets were correctly balanced. Anyway, I removed the obsolete comment [6] and Popups works well now. Fiji has a long infobox code. Wikipedia:Tools/Navigation popups#Options says: "popupMaxPreviewCharacters | 600, an integer | The maximum number of characters to extract from something approximating the beginning of an article for the preview." The Fiji popup only displays "Fiji ( , ; " with the default 600. That's not an error but just an unfortunate result of skipping templates and cutting off before the closing parentheses and following normal text is reached. It works well with window.popupMaxPreviewCharacters = 6000; in your common JavaScript. It still only gives "Fiji ( , ; " with 5000 so the default 600 is far from reaching a good result here. PrimeHunter (talk) 10:59, 10 July 2024 (UTC)Reply

Ah, thanks for tracking that down. I've added the javascript. I suppose for an opt-in gadget the few failures at 600 is probably acceptable. If the main Page Previews had the issue it would be more of a concern. I thought I'd checked that the error was Page Previews, not Navigation Popups, so clearly screwed up there. —  Jts1882 | talk  12:45, 10 July 2024 (UTC)Reply

I have a question concerning the custom formatting options of TemplateData, specifically for {{Episode table}}.

I noticed that when editors edit this particular template in Visual Editor, VE would remove all the spacing between the parameters. To fix this, I added custom formatting of the paramaters into the TemplateData to keep the spacing. It worked! However, with this fix, the new issue is now the removal of just the spacing after the last parameter, which I then need to restore manually.

In these examples linked, every other parameter declaration and value for {{Episode table}} can be displayed inline; however, |episodes= spans multiple lines, and its value should begin on the line after the parameter declaration.

My question is: how can I add spacing to the custom formatting for just the last parameter, to prevent this sort of removal? -- Alex_21 _TALK 10:06, 10 July 2024 (UTC)Reply

This is not possible. Izno (talk) 21:36, 10 July 2024 (UTC)Reply

That's unfortunate; I did think that might be the case. Does that mean the sort of edit in that last link is not something that can be automatically fixed? -- Alex_21 _TALK 01:39, 11 July 2024 (UTC)Reply

Can someone with the knowledge apply Template:Resolve category redirect to the whole of Template:Country establishment category by century. Currently the latter is causing Category:Medieval Belgium to be populated instead of Category:Medieval history of Belgium. Thanks in advance. Timrollpickering (talk) 10:31, 10 July 2024 (UTC)Reply

@Timrollpickering: I currently see no pages in Category:Medieval Belgium and the mentioned templates haven't been edited recently. Please give a clear example of the perceived problem, e.g. a page you saw in a wrong category if that was the problem. Maybe it was automatically fixed by a delayed process rendering the affected pages again and updating link tables after yesterdays move of Category:Medieval Belgium to Category:Medieval history of Belgium. PrimeHunter (talk) 11:13, 10 July 2024 (UTC)Reply

Please create the following redirect:

• 2022 FIBA U18 Women's Asian Championship → 2022 FIBA Under-18 Women's Asian Championship

I was going to do it myself, but this redirect page is fully protected. Thanks, Maiō T. (talk) 14:12, 10 July 2024 (UTC)Reply

  Done * Pppery * _{it has begun...} 02:03, 11 July 2024 (UTC)Reply

The latest run of Special:WantedCategories features a redlinked ‹The template Category link is being considered for merging.› Category:Philippine articles requiring maintenance, populated by the single page Liloan — and while the redlink obviously has to either get created or go away, that's not the only reason I'm bringing it to VPT: the page itself is absolutely buried in blaring red template-error messages, like tables smothered in "Formatting error: invalid input when rounding" and an Economy section that consists entirely of the text "Lua error in Module:Chart at line 301: bad argument #1 to 'max' (number expected, got string)." with no actual economic data, and even an external link that's been drowned in multiple instances of "String Module error: String subset index out of range".

The page was moved within the past 48 hours from the former title Liloan, Cebu, so this may stem from a mismatch between its new title and the title the templates are expecting, but I wouldn't know how to fix that. So could somebody with more skill in that area than I've got look into this page and figure out what's causing the errors? Thanks. Bearcat (talk) 14:52, 10 July 2024 (UTC)Reply

This came from Wikidata not being properly updated after the move, which I've now fixed. * Pppery * _{it has begun...} 14:59, 10 July 2024 (UTC)Reply

Ah, OK. Great, thanks much! Bearcat (talk) 15:00, 10 July 2024 (UTC)Reply

Weird - I just installed Chrome on a new computer, and it is ignoring all my preferences - scripts, etc. No scripts show up (Twinkle, etc.), heck, it even does not allow me to enable visual editor. Heck, even clicking 'add topic' in Chrome on this very page here doesn't work. Microsoft Edge which I used on that computer for few days works fine (all tools/etc. show up and work), and obviously I can post here. Seems like some Chrome issue (not Wiki preferences issue) - any idea what settings to play with? No, clearing cache etc. doesn't work. _{Piotr Konieczny aka Prokonsul Piotrus| reply here} 12:08, 11 July 2024 (UTC)Reply

Sounds like maybe you have Javascript disabled ? Did you install/restore a chrome extension that maybe has that as a default ? —TheDJ (talk • contribs) 12:15, 11 July 2024 (UTC)Reply