Wikipedia:Interface administrators' noticeboard

Welcome to the interface administrators' noticeboard

This is the interface administrator noticeboard, for discussion of interface administrators and coordination of edits to the interface.

Currently only interface administrators can undelete JS/CSS pages, if you have an uncontroversial undelete or deleted version retrieval request, please list it below.

Any administrator can delete JS/CSS/JSON pages, for speedy deletions just use a CSD template on the page or its talk page.

Individual requests for edits to interface or user JavaScript/CSS pages should continue to be made on their respective talk pages.

Click here to start a new discussion

0 interface-protected edit requests
Page Tagged since Protection level Last protection log entry
Updated as needed. Last updated: 18:44, 26 May 2026 (UTC)

Phlogiston enthusiast, which is me, has blocked themself by accident untill the year 9999.

I was testing if the auto wikibreak script could safeguard against user error, such as typing 2026 as 3026. It cannot. Please someone fix this. My user is user:Phlogiston Enthusiast. I have set the break to end in the year 9999. ~2026-23621-13 (talk) 20:44, 16 April 2026 (UTC)

Already  Done. Diff. Welcome back. –Novem Linguae (talk) 06:33, 17 April 2026 (UTC)

Indefinite blocks now saying "infinite" instead of "indefinite"

I thought I was the only one that noticed blocks now say "infinite" instead of "indefinite" but seems like someone started a discussion about it at WT:Blocking policy#Why does "indefinite" block say "infinite" now??. Does anyone know why it now does? Another user suggested that a recent UI change may of been the cause of this (which may also explain why I keep seeing mobile edits with the summary "/*(top)*/" ). --Prothe1st (leave me a message)-- 22:35, 12 May 2026 (UTC)

Relevant page is MediaWiki:Ipboptions, @Xaosflux recently edited it (removing the "indefinite" label, which seemingly reverted it to the MediaWiki default of "infinite") with the edit summary ok it is redundant to the new UI. Looks like it was an accident, as it wasn't redundant after all – Xaosflux, mind if I revert it? Chaotic Enby (talk · contribs) 22:52, 12 May 2026 (UTC)

So I thought it wasn't - but it is, because the block UI changed - and now "indefinite" is on the radio selection, above where you would use the radio selection to get this list. — xaosflux ^Talk 00:02, 13 May 2026 (UTC)

Clicking indefinite there still causes "infinite" to be listed in the block log as I discovered when blocking Testkeep49. Infinite also appears in the drop-down menu for duration which I discovered when doing an actual block. Best, Barkeep49 (talk) 00:05, 13 May 2026 (UTC)

The change occurred some time between 1 May and 13 May, and whatever changed has changed all historical entries. So it's not the input, but the display that's been affected. Xaosflux's change was on 6 May. I'd interpret that as our little hack of using indefinite:indefinite having some effect on the display of historical data, and worth trying a revert (assuming we agree that it's an issue). I don't really see having indefinite in that dropdown as an issue, fwiw. -- zzuuzz ^(talk) 17:30, 14 May 2026 (UTC)

The drop-down list of durations used to have two entries, one "indefinite" and the other "infinite"; of these, one was at the top and one at the bottom, but I don't recall which way round they were. I always wondered (a) whether there was any practical difference, and if not, (b) why were both necessary. The list now has only one, "infinite", and it's at the bottom, so in future when blocking I will need to scroll down to find it. I guess that's a safety thing, so that selecting it is now a conscious action, rather than accidentally picking the first option when a short block was intended. --Redrose64 🌹 (talk) 21:27, 14 May 2026 (UTC)

Special:Diff/880298592 seems to indicate that it used to display "indefinite" at the top and bottom, but then when the form was switched to OOUI that didn't like having two entries with the same text. As for why it was on there twice, that seems to go back to MediaWiki talk:Ipboptions/Archive 1#sequence of options in 2006. The reason given back then was "to allow for quicker blocks in emergency cases". Anomie⚔ 23:19, 14 May 2026 (UTC)

Looking in the code, I find that the code looks for the first entry in MediaWiki:ipboptions where the value is any of 'infinite', 'indefinite', 'infinity', or 'never' and uses that key. If we don't want to add "indefinite:indefinite" back to the top of the list, we could instead change the "infinite:indefinite" at the end to "indefinite:indefinite". Anomie⚔ 23:12, 14 May 2026 (UTC)

Just tested it on testwiki:MediaWiki:Ipboptions (it can be seen in action at testwiki:Special:Contributions/Chaotic Enby), looks like your fix works! I presume we can go ahead with it if no one else sees any issues with doing so? Chaotic Enby (talk · contribs) 23:27, 14 May 2026 (UTC)

Please do.

I think the format is adequately described here, so having a localisation be "indefinite:infinite" will display the expiry as "indefinite" even if it is set as "infinite". I do wonder if there is a way to change it to "no expiry set:infinite" to be consistent with MediaWiki:Infiniteblock though. Aasim (話す（はなす）) 14:19, 15 May 2026 (UTC)

 Please, done. Chaotic Enby (talk · contribs) 14:28, 15 May 2026 (UTC)

Sibling project icons in side bar

Please implement the consensus reached at Wikipedia:Village pump (technical)#Sibling project icons in side bar. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:15, 24 May 2026 (UTC)

After a quick glance, the situation seems a bit more complex than I imagined. (or its specialized Vector.css or Vector-2022.css) don't have these equivalents. Still looking for the CSS code to not mess up the implementation! Chaotic Enby (in solidarity · talk · contribs) 17:14, 24 May 2026 (UTC)

Nevermind, it's just in Gadget-InterProjectLinks.css. I'll add it and the JS after a quick check (and testwiki test). Chaotic Enby (in solidarity · talk · contribs) 17:32, 24 May 2026 (UTC)

Done! I've added it as an opt-in gadget for now: while the consensus is to have it on by default, it could be good to have it opt-in for a few hours/days to make sure there aren't any glaring bugs I've overlooked. Please ping me either way! Chaotic Enby (in solidarity · talk · contribs) 17:59, 24 May 2026 (UTC)

Thank you. It's working well for me. so far. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:18, 24 May 2026 (UTC)

Just out of curiosity, I'm wondering what are the pros/cons to the Nlwiki version (which includes JavaScript & CSS - InterProjectLinks.js and InterProjectLinks.css) versus the pure-CSS Dewiki userscript-version (also linked in the VPT thread). They seem to function the same in my quick tests, and I'd normally guess that the 'simpler is better' CSS-only version is preferable, hence I'd like to learn more about how the JS is helping/necessary. (i.e. I don't quite understand what all parts of the JS are doing.... does something in there fix edge-cases? or improve accessibility?). Cheers. Quiddity (talk) 19:53, 24 May 2026 (UTC)

For the Main Page, the JS is only there to fix edge cases in case the class names are missing, it's very much not crucial. The class names seem to be there by default in Vector 2010 and 2022, although I haven't checked the other skins.

For other pages, the script also retrieves links from {{InterProject}} (which generates a div set to display: none; for that purpose) and adds them to the sidebar. If we only care about the icon part, it's not needed. Chaotic Enby (in solidarity · talk · contribs) 20:11, 24 May 2026 (UTC)

Thanks for the details! (Now I'm confused about whether our {{InterProject}} actually does anything useful...?! But I don't have the spoons left to dig further.) Cheers, Quiddity (talk) 23:33, 24 May 2026 (UTC)