Wikipedia:Village pump (technical): Difference between revisions

Browse history interactively

← Previous edit

Content deleted Content added

VisualWikitext

Inline

Latest revision as of 06:13, 2 August 2024

Table of contents
First discussion
End of page
New post

Shortcuts

The technical section of the village pump is used to discuss technical issues about Wikipedia. Bug reports and feature requests should be made in Phabricator (see how to report a bug). Bugs with security implications should be reported differently (see how to report security bugs).

If you want to report a JavaScript error, please follow this guideline. Questions about MediaWiki in general should be posted at the MediaWiki support desk. Discussions are automatically archived after remaining inactive for five days.

view · edit

Frequently asked questions (see also: Wikipedia:FAQ/Technical)

Click "[show]" next to each point to see more details.

If something looks wrong, purge the server's cache, then bypass your browser's cache.
This tends to solve most issues, including improper display of images, user-preferences not loading, and old versions of pages being shown.

No, we will not use JavaScript to set focus on the search box.
This would interfere with usability, accessibility, keyboard navigation and standard forms. See task 3864. There is an `accesskey` property on it (default to `accesskey="f"` in English). Logged-in users can enable the "Focus the cursor in the search bar on loading the Main Page" gadget in their preferences.

No, we will not add a spell-checker, or spell-checking bot.
You can use a web browser such as Firefox, which has a spell checker.

If you have problems making your fancy signature work, check Help:How to fix your signature.

If you changed to another skin and cannot change back, use this link.
Alternatively, you can press Tab until the "Save" button is highlighted, and press Enter. Using Mozilla Firefox also seems to solve the problem.

If an image thumbnail is not showing, try purging its image description page.
If the image is from Wikimedia Commons, you might have to purge there too. If it doesn't work, try again before doing anything else. Some ad blockers, proxies, or firewalls block URLs containing /ad/ or ending in common executable suffixes. This can cause some images or articles to not appear.

For server or network status, please see Wikimedia Status. If you cannot reach Wikipedia services, see Reporting a connectivity issue.

« Archives, 194, 195, 196, 197, 198, 199, 200, 201, 202, 203, 204, 205, 206, 207, 208, 209, 210, 211, 212, 213, 214

Adding documentation subpage to module doc pages

Currently, {{Documentation subpage}} is added to module doc pages with MediaWiki:Scribunto-doc-page-header. The problem with this approach is that the system message does not add Category:Module documentation pages. If we want to add it, we have to either transclude {{Documentation subpage}} ourselves, which makes it appear twice, or add the category directly, which makes it much harder to update in case the category is moved in the future.

I have gone with the second approach for now by editing Template:Documentation/preload-module-doc to add the category, but I don't think that it's a good idea. What we should do instead is blank MediaWiki:Scribunto-doc-page-header and transclude {{Documentation subpage}} manually to all the module doc pages, as was suggested in MediaWiki talk:Scribunto-doc-page-header § Category:Module documentation pages. Nickps (talk) 16:01, 25 July 2024 (UTC)[reply]

Note: I originally intended to ask the devs to make the system message add the category but this has been proposed in the past in phab:T289404 and was declined. This is why I think adding the template manually is the best approach. Nickps (talk) 16:03, 25 July 2024 (UTC)[reply]

(edit conflict) This is yet another proposal to make a huge number of edits to accomplish something of very questionable value. Not worth it IMO. * Pppery * _{it has begun...} 16:04, 25 July 2024 (UTC)[reply]

The code for {{Documentation subpage}} has a test that looks like it tries to assign a category:

... [[Category:{{#switch:{{SUBJECTSPACE}} |Template=Template |Module=Module |User=User |#default=Wikipedia}} documentation pages]] ...

. My naive question is: why isn't that code working? Does an if statement need to be redesigned? Can something else be tweaked inside that template? I'm not clear on how the page-header page "adds" the doc subpage to the template without actually transcluding it; maybe the category could be "added" in the same way that the doc subpage template is "added". – Jonesey95 (talk) 16:19, 25 July 2024 (UTC)[reply]

@Jonesey95: The template works fine. The problem is that system messages do not add categories (see phab:T289404). If the template is included directly to a page, like in Module:Citation/CS1/doc, the categorisation works as intended. That's what I want to do, but if MediaWiki:Scribunto-doc-page-header isn't blanked first, people will see the message appear twice, assume it's a mistake and remove the template. Nickps (talk) 16:23, 25 July 2024 (UTC)[reply]

I'm more inclined to just delete Category:Module documentation pages. Unlike its twin Category:Template documentation pages which isn't very useful as a category but requires no effort to populate, this requires a lot of effort and the value over CirrusSearch isn't large enough to justify it. * Pppery * _{it has begun...} 16:35, 25 July 2024 (UTC)[reply]

And I fixed a lot of them with a single edit. It really won't take as much effort as you think. Nickps (talk) 16:44, 25 July 2024 (UTC)[reply]

@Nickps: Could you please stop making these edits until there's consensus that they should be done? You're creating a dangerous fait accompli. * Pppery * _{it has begun...} 17:06, 25 July 2024 (UTC)[reply]

I will stop. But you're not explaining what's so dangerous about them. They can be reverted as easily as I am doing them. Nickps (talk) 17:07, 25 July 2024 (UTC)[reply]

10 minutes of edits done manually can be reverted in less than half that by someone with AWB. I'm not creating a fait accompli and I'd like you to take that back. Nickps (talk) 17:11, 25 July 2024 (UTC)[reply]

You've been doing this for over an hour, not 10 minutes. * Pppery * _{it has begun...} 17:13, 25 July 2024 (UTC)[reply]

Fair, I lost track of time, I guess. Still, really easy to revert. Nickps (talk) 17:17, 25 July 2024 (UTC)[reply]

(edit conflict) What's dangerous is explained in the essay I linked - it inappropriately biases the situation toward the automatic documentation being removed later because the edits required to do it are already in place. The cost of this is that every time a module is created {{documentation subpage}} has to be manually added to the subpage forevermore, and I'm not seeing what the point of Category:Module documentation pages even is when the search I linked above can produce the same output in the unlikely event anyone cares. * Pppery * _{it has begun...} 17:12, 25 July 2024 (UTC)[reply]

I've just nominated Category:Module documentation pages for deletion. * Pppery * _{it has begun...} 17:17, 25 July 2024 (UTC)[reply]

What we should do instead is blank MediaWiki:Scribunto-doc-page-header and transclude {{Documentation subpage}} manually to all the module doc pages – this sounds as a good workaround for phab:T289404 to me. It will a) make Category:Module documentation pages useful on watchlists and b) make /doc pages consistent, because right now some /doc subpages of modules end up with two banners.

As I mentioned at the category deletion discussion, using the preload template won't require a lot of effort to populate Category:Module documentation pages. —⁠andrybak (talk) 22:47, 27 July 2024 (UTC)[reply]

Display of Text Image is Distorted

Hello, I found a problem on Commons. The problem is with images in SVG format, where there is distortion in the display of the text of the image, a change in the location of the text display, and a difference in the size of the text display.

This is a sample image, please click and view. So if you click on it, it will appear to you like this.

I thought the problem was due to the program I use to edit photos. For about a full day, I was experimenting with solving the problem, trying different size dimensions and so on, but it was not solved. Then in the end I discovered that the cause of the problem was the Commons website and not me.

I was also able to find out the reason for the problem on the Commons website. It occurs because the text is in a large size, and if you reduce it, the text size will be displayed at approximately the correct size.

Therefore, I ask that the technicians responsible please fix this defect, because it is a major problem. I have stopped editing images until the problem is fixed. Unfortunately, many people must have stopped designing images in this format and uploading them to Wikipedia articles because of this problem.

Note: I do not want to raise the discussion within the Commons project, because it is a very important problem related to the display of images in Wikipedia articles, and Because there is no interest from technicians within the Commons project. Mohmad Abdul sahib talk☎ talk 21:55, 25 July 2024 (UTC)[reply]

How do you know technicians from the Commons project wouldn't be interested in this issue if you haven't raised it there? Tule-hog (talk) 22:06, 25 July 2024 (UTC)[reply]

@Tule-hogYou can take a look here There are problems raised a year ago that have not been answered. Also, the problem I raised is urgent and important. I have stopped all my projects until the bug is fixed. In addition, the problem is linked between the two projects. Mohmad Abdul sahib talk☎ talk 19:42, 26 July 2024 (UTC)[reply]

Not saying you shouldn't have raised it here, just that you might also try raising it there to increase coverage. Arabic's SVG rendering possibly not working is a serious, global bug to be sure. Have you happened to find any graphics that don't have the issue? Tule-hog (talk) 02:58, 27 July 2024 (UTC)[reply]

I think the problem is that your used the Arial font in your image, which is not a free font, and thus is not installed on the Wikimedia servers. Try changing the text in the image to use one of the fonts listed here: https://meta.wikimedia.org/wiki/SVG_fonts – I suggest Liberation Sans, which was designed as an alternative to Arial – and see if that makes it display right. Matma Rex talk 22:28, 26 July 2024 (UTC)[reply]

@Matma Rex: Nope. I have tried (LiberationSans-Bold), and the problem is the same. There has only been a slight difference in text measurements, but text distortion, positioning, and size are still there. Mohmad Abdul sahib talk☎ talk 02:50, 27 July 2024 (UTC)[reply]

Hmm, you're right. I uploaded a new version of the file (File:Anterior Thyroid - Arabic.svg) just to be sure, and it still looks very wrong. I want to try some other things, but I'm not sure how the result is supposed to look like – the SVG file on my computer also has slightly weird-looking text, and I'm not sure if it's a problem with the file or with my applications: https://phabricator.wikimedia.org/F56717722. Can you export it to PNG on your computer and upload that version to Commons too, so that we may compare? Matma Rex talk 03:34, 27 July 2024 (UTC)[reply]

@Matma Rex: I think I discovered the cause of the problem, it is caused by a difference in dots per inch. Because I downloaded an image in SVG format for the year 2010 and wanted to modify it, but I saw this message inside the program:

was created in an older version of Inkscape (90 DPI) and we need to make it compatible with newer versions (96 DPI). Tell us about this file. This file contains digital artwork for screen display (Choose if unsure.) This file is intended for physical output, such as paper or 30 prints. Create a backup file in same directory. More details: We've updated Inkscape to follow the CSS standard of 36 OPI for better browser compatibility we used to use 50 DPI. Digital artwork for screen. display will be converted to 96 DPI without scaling and should be unaffected. Artwork drawn at 90 DPI for a specific physical size will be too small if converted to 96 DPI without any scaling. There are two scaling methods. Scaling the whole document: The least error-prone method, this preserves the appearance of the artwork, including filters and the position of masks etc. The scale of the artwork relative to the document size may not be accurate. Scaling individual elements in the artwork: This method is less reliable and can result in a changed appearance but is better for physical output that relles on accurate sizes and positions (for example for 3D printing. More information about this change are available in the Inliscape

I have installed Inkscape version 0.48 (2010). Then I tried editing the image and uploading it to Commons, and I did not see any distortion or any problems with the text. __________________ There is another problem, which is when you open the image in this way, right-click on it and then download it directly, without clicking on the download icon, the image is not downloaded in SVG format, but rather in PNG format, and this is a big problem that should not happen. Mohmad Abdul sahib talk☎ talk 04:55, 27 July 2024 (UTC)[reply]

@Matma Rex: This is the original image. We do not have distortion problems with PNG images because their texts are more like printed matter or more like hardsub, meaning that the text is not editable, nor are the image objects. As for SVG files, they are more like an image project that can be edited and translated, including the text. I work with SVG images so that they can be easily modified and translated into other languages. I hope in the future that Wikipedia's policy will change so that it does not allow uploading any PNG images of any images with text on them.

In fact, I suggest that Wikipedia provide the feature of translating SVG image texts without the need to upload them repeatedly for each language. This will facilitate the work and reduce the size of the Commons server data. I mean, if the Commons project provides us with the advantage of recognizing image texts and translating them so that they are displayed directly without the need to repeatedly upload the image in each language, then the matter will become easier and faster and will save space on the Commons project server. Mohmad Abdul sahib talk☎ talk 05:16, 27 July 2024 (UTC)[reply]

SVG image rendering is done using librsvg, if you have problems with how the image renders it is probably a problem in the librsvg library. We don't do direct work on developing the software that renders the SVG (it is a dependency). If you find the issue, perhaps you can report it with the librsvg project. —TheDJ (talk • contribs) 08:50, 27 July 2024 (UTC)[reply]

" I suggest that Wikipedia provide the feature of translating SVG image texts without the need to upload them repeatedly for each language" You are welcome to write such functionality for MediaWiki. Most of this kind of functionality is written by volunteers. —TheDJ (talk • contribs) 08:58, 27 July 2024 (UTC)[reply]

In fact there is a tool for this already: commons:Commons:SVG Translate tool. the wub "?!" 10:12, 27 July 2024 (UTC)[reply]

The user stated they wish to do this without having to reupload for each translation. While svg translate allows combining translations into a single upload, each edit to them or each new translation still requires a reupload. —TheDJ (talk • contribs) 08:54, 28 July 2024 (UTC)[reply]

This is in German, but it's the *same* image

Jarry1250 (talk · contribs) (a former VPT regular, but still around from time to time) has already shown us how this may be done, see Wikipedia:Village pump (technical)/Archive 96#SVG translation. If you go to the file description page, you should see a "Render this image in" dropdown - pick something from that. It makes use of the switch element in SVG. --Redrose64 🌹 (talk) 10:51, 27 July 2024 (UTC)[reply]

"right-click on it and then download it directly" then you are downloading the thumbnail, and this is expected. If you want the original file, you always need to use the link below it "original file" and choose Save file as. —TheDJ (talk • contribs) 08:48, 27 July 2024 (UTC)[reply]

Thanks for all this information.

@TheDJ: yes, I know this. I meant that the image must be downloaded in SVG format even if it is clicked directly without clicking on the download icon - otherwise some people may not pay attention to the download icon and a problem and suspicion will occur.

@The wubThe wub: This is something legendary, I didn't know about it. But I have a problem, which is when I access a Commons project in English, its interface will switch to Arabic. Unfortunately, the Commons project cannot be accessed according to the desired language، and unfortunately, the (Content Translation/V2) is not available in this project, and for this reason I cannot translate many explanatory articles in the Commons project. I hope that the Commons:SVG Translate tool icon is present on the information page of every SVG image uploaded to Commons, so that everyone knows that this feature exists, whether writing on images or translating them.

I have informed the members of the Librsvg project, and am waiting for their response to find out if the problem is due to the library. We still need to find out the cause of the malfunction, to determine the cause of the problem, any information about this would be helpful. I hope that we will cooperate in fixing the defect, because the problem is related to a major error related to Wikipedia, especially the display of images. I have currently stopped all my projects related to image design, because if I now upload images with small texts in them so that they will be displayed in a large size, it is expected that after fixing the defect, the text size will decrease.Mohmad Abdul sahib talk☎ talk 08:05, 28 July 2024 (UTC)[reply]

@Mohmad Abdul sahib: Regarding the Commons project cannot be accessed according to the desired language - have you checked that the setting at c:Special:Preferences#mw-prefsection-personal-i18n is correct? --Redrose64 🌹 (talk) 09:53, 28 July 2024 (UTC)[reply]

I have opened a report here. I cannot handle the issue and follow up the problem programmatically, because I am not a programmer. By opening the issue in the Librsvg project forum, it becomes clear that following up on the problem and diagnosing its cause is the responsibility of Wikipedia members. I did everything I could do, and the rest requires your intervention. Mohmad Abdul sahib talk☎ talk 17:40, 28 July 2024 (UTC)[reply]

Can anybody provide us with report information here?Mohmad Abdul sahib talk☎ talk 02:46, 2 August 2024 (UTC)[reply]

@Mohmad Abdul sahib: AKlapper (WMF) (talk · contribs) has already told you why it's not a matter for Gnome. --Redrose64 🌹 (talk) 06:13, 2 August 2024 (UTC)[reply]

dark mode on Wikipedia

i'm repeating myself, but: 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?

Maybe something like Wikipedia:Centralized discussion?

--173.67.42.107 (talk) 07:46, 26 July 2024 (UTC)[reply]

dark text on a light background in dark mode

Parts of these pages have dark text on a light background in dark mode:

color-coded tables on list of minor planets: 7001–8000
- color-coded tables on list of minor planets
  - That page also has some charts that are mostly white. Of course image files don't change color (well, GIF files might, but i don't think they're the solution here), but it's something else to consider.
In Wikipedia:Village_pump_(technical)/Archive_42,

this part

Village pump (Policy - Technical - Proposals (persistent) - Idea lab - WMF - Miscellaneous)

and this part

Village pump (technical) archive
This page contains discussions that have been archived from Village pump (technical). Please do not edit the contents of this page. If you wish to revive any of these discussions, either start a new thread or use the talk page associated with that topic.
< Older discussions · Archives: A, B, C, ... 212, 213, 214

appear as dark text (including blue links that turn purple after clicking them) on a light background. The list of archives includes 42 as hard-to-see #light text on a light background in dark mode.

The GIF article has an infobox that says (more or less)

Filename extension: .gif
Internet media type: image/gif
Type code: GIFf
Uniform Type Identifier (UTI): com.compuserve.gif
Magic number: GIF87a/GIF89a

but ".gif", "image/gif", and "GIFf" appear as dark text on a light background. "GIF87a" and "GIF89a" seem to switch with light mode/dark mode, maybe by using <code>THIS</code> instead of {{code|THAT}}?

Thanks and good luck, you Wikipedia hackers, code crackers, slackers, wasting time with all the talk page blackeners.

--173.67.42.107 (talk) 07:46, 26 July 2024 (UTC)[reply]

"Parts of these pages have dark text on a light background" yes this is expected. There is 25 years of legacy and fixing all these templates to have both a light AND a dark mode will take multiple years and require new decisions to be made. The highest priority however right now is to ensure we do not have dark on dark or light on light, as that effects readability. The 'is it pretty' issues will be dealt with in good time. —TheDJ (talk • contribs) 08:55, 27 July 2024 (UTC)[reply]

Agreed: This is not a top priority. However, as someone unfamiliar with coding, i don't always know if a problem here is related to a problem there, so sometimes i ask others i think might know (or might know how to find out). Also, even if the issues are unrelated, a small issue might still deserve to be on the to do list (even if way, way down on the to do list), so i hope mentioning it is useful. --173.67.42.107 (talk) 19:44, 27 July 2024 (UTC)[reply]

TheDJ, well, in this case it's a combination of the SyntaxHighlight extension not supporting dark mode, which we can't do much about, and {{code}} using the syntaxhighlight tag, when it could use the code tag if no langauge is specified. — Qwerfjkl talk 19:56, 27 July 2024 (UTC)[reply]

light text on a light background in dark mode

As mentioned above:

In Wikipedia:Village_pump_(technical)/Archive_42, the 42 is hard-to-see light text on a light background.

--173.67.42.107 (talk) 07:46, 26 July 2024 (UTC)[reply]

dark mode on laptop

i've done a bit of Wikipedia browsing and editing on my smartphone, mostly in dark mode since i learned it was an option (Wednesday July 10?).

On my laptop, wikipedia.org addresses redirect by default to en.wikipedia.org and light mode, but i have sometimes edited the web address to en.m.wikipedia.org to get the mobile dark mode on my laptop.

Today (Saturday July 27) on my laptop, en.wikipedia.org (i think it was en.wikipedia.org/wiki/Wikipedia:Sandbox if that matters) gave me a pop-up alert saying something along the lines of "dark mode is available in the Appearance link of the menu on the right side of the screen" but i can't find Appearance listed in any of the five menus i've found:

The upper right of the screen has three dots resembling an ellipsis... that gives me this drop down menu:

Pages for logged out editors (learn more)

Contributions

Talk

below that is the drop down menu for languages (obviously Appearance doesn't belong there)
below that is a Tools drop down menu (i can list its options if that would help, but Appearance isn't one of them, even when i scroll down as far as it goes, so...)
The upper left has what looks like a triple bar or 三 that reveals a drop down Main menu (again, i can list the options, but Appearance isn't there, even scrolling to the bottom)
below that is the drop down table of Contents, resembling a vertical ellipsis next to a triple bar, somewhat like ⋮Ξ (again, Appearance doesn't belong there, although as a pictograph it looks like it could be a settings menu)

Appearance is also not visibly part of the footer "menu":

Privacy policy

About Wikipedia

Disclaimers

Contact Wikipedia

Code of Conduct

Developers

Statistics

Cookie statement

Mobile view

i also checked Wikipedia's Main Page with similar results (no Appearance nor ⋮三).

i exited the pop-up in search of the Appearance link and have not been able to get the pop-up again (which is normally a good thing, but right now means i can't double check anything about it, like, "did it say Appearance or appearances?")

If anyone knows what's going on here, please don't leave me in the dark. i mean, let me in on the dark. You know what i mean. ;-)

--173.67.42.107 (talk) 19:44, 27 July 2024 (UTC)[reply]

Are you looking for the little set of eyeglasses next to the "Create account" link? – Jonesey95 (talk) 21:00, 27 July 2024 (UTC)[reply]

Start a discussion notice on Talk pages

Tracked in Phabricator
Task T371125

Usually the start discussion notice is displayed on talk pages with no comments; But, now its in all talk pages. Even in Wikipedia talk:Village pump (technical), Don't know how long it has been but I just noticed it. Is it a glitch or something??? Vestrian24Bio (TALK) 11:48, 26 July 2024 (UTC)[reply]

@Vestrian24Bio I don't see that notice on Wikipedia talk:Village pump (technical), and I don't see it on other random talk pages I checked (e.g. Talk:The Fighting Temeraire). I see it on e.g. Talk:Anna Nagar railway station, but that page has no comments (just a very big talk header), so that is expected.

Can you share a screenshot of how these talk pages look for you? (You can upload screenshots more easily on Phabricator: [1].) Matma Rex talk 13:58, 26 July 2024 (UTC)[reply]

@Matma Rex I've took screenshots of Wikipedia talk:Village pump (technical) and Talk:Deadpool & Wolverine but, I'm unable to upload them now due to network constraints. I'll try to do it later; but for now the screenshots can be viewed here: [2] [3]

FYI: The notice appears on bottom of the page. Vestrian24Bio (TALK) 14:24, 26 July 2024 (UTC)[reply]

@Vestrian24Bio Oh, I see! You have enabled the new Parsoid wikitext parser at Special:Preferences#mw-prefsection-editing-developertools (as evidenced by the "Rendered with Parsoid" badge visible in your screenshots – thank you for sending them!). I can reproduce the problem when I do that. I don't know why it happens, but I filed a bug about it: T371125. Matma Rex talk 16:34, 26 July 2024 (UTC)[reply]

Okay, Thanks.

Vestrian24Bio (TALK) 17:22, 26 July 2024 (UTC)[reply]

Is there an option to remove/hide this large notice (even on talk pages with no comments)? ~ Tom.Reding (talk ⋅dgaf) 11:41, 30 July 2024 (UTC)[reply]

There isn't, but you could hide it using personal CSS. Matma Rex talk 11:55, 30 July 2024 (UTC)[reply]

@Matma Rex: that's great! Would you know how? ~ Tom.Reding (talk ⋅dgaf) 18:22, 30 July 2024 (UTC)[reply]

@Tom.Reding Edit your personal CSS page: Special:MyPage/common.css and add the following there:

.ext-discussiontools-emptystate {
  display: none !important;
}

There is a (terribly outdated) help page about this feature at Help:User style. Matma Rex talk 09:25, 31 July 2024 (UTC)[reply]

List of cities proper by population density

The list starts at #2, instead of #1. Can someone make the necessary fix? Home Lander (talk) 23:41, 26 July 2024 (UTC)[reply]

It looks right to me, with no edits since the 22nd? —Cryptic 00:02, 27 July 2024 (UTC)[reply]

Done It wasn't. Just fixed it. •Shawnqual• 📚 • 💭 00:21, 27 July 2024 (UTC)[reply]

Thanks, would have never gotten that by myself. Home Lander (talk) 17:07, 27 July 2024 (UTC)[reply]

Now do a list for “proper cities”. 😉 Blueboar (talk) 17:19, 27 July 2024 (UTC)[reply]

Done, if you meant the List of metropolitan areas by population density. •Shawnqual• 📚 • 💭 01:54, 29 July 2024 (UTC)[reply]

Table covers appearance settings

On List of Anaheim Ducks seasons, when you view the page logged out and scroll down far enough, the year by year table partially covers up the appearance settings (in Google Chrome, Windows 11, for what it's worth). I'm guessing this probably isn't intended; is there a means of nudging the settings over so they are fully visible for users? Home Lander (talk) 17:06, 27 July 2024 (UTC)[reply]

This is a known issue that WMF developers have been poking at ever since they rolled out Vector 2022 as the default skin. The main task is T361737. – Jonesey95 (talk) 19:38, 27 July 2024 (UTC)[reply]

Per mw:Recommendations for mobile friendly articles on Wikimedia wikis you can mark large tables up so that they scroll (I did that for this article). This issue has been around for over a decade now for mobile users. Vector 2022 just brought the issue to a larger audience.

The referenced issue (if solved) will likely be resolved by marking up tables like this automatically but I don't think there is a silver bullet for fixing every table (this solution is incompatible with sticky headers for example). 🐸 Jdlrobson (talk) 02:24, 28 July 2024 (UTC)[reply]

Removing the need for round robin moves

I am not sure if this is the right forum. Feel free to move it to a proper one, such as WP:Village pump (idea lab).

When page A needs to be renamed to B, but B redirects to A, what commonly happens is that B gets moved to C without leaving a redirect (so that page B is free), meaning A can then be renamed to B, and C can be renamed to B, also without leaving a redirect. This is called a round robin move. Alternatively, the redirect B can simply be deleted. Since this is commonly done, is it feasibility and technically possible to do the two moves at the same time (eg, A to B and B to A at the same time), removing the need for a third one? JuniperChill (talk) 19:35, 27 July 2024 (UTC)[reply]

phab:T303120 is a declined feature request "Swapping pages". PrimeHunter (talk) 20:04, 27 July 2024 (UTC)[reply]

Dark mode images with transparent color

The UK Space Agency article has a logo at the top which is supposed to have the red, blue and white colors of the union jack, however the image doesn't actually use white, it uses transparent so it blends in with the off-white panel. However in dark mode the transparent area appears black so the logo appears red, blue and black which is wrong. The solution would be for images not to use transparent colors when they should be white although this would upset people who want the image to blend in with the off-white background panel. Termynaytor (talk) 04:45, 28 July 2024 (UTC)[reply]

If it should be white, someone needs to fix the logo. Misrepresenting logos is a miss on our part. Izno (talk) 04:59, 28 July 2024 (UTC)[reply]

Agreed. If a logo is truly intended to be transparent background, we should use that, of course. But that is the rarity. I'm not one for "catering" to companies/organizations' preference, but in the display of their logos (whether it's a white background or otherwise) we should follow their press/media kits for displaying it - at least in the color department. The vast majority of organizations will have their logo as part of a press/media kit with guidance on how it is to be shaped, the colors to use (often with exact hex values) - and we should use logo images that comply with those even if they are public domain, in my opinion. -bɜ:ʳkənhɪmez (User/say hi!) 05:23, 28 July 2024 (UTC)[reply]

See also discussion started at Template talk:Infobox company#Logos_in_dark_mode. -- WOSlinker (talk) 06:55, 28 July 2024 (UTC)[reply]

@Izno and Berchanhimez: The official website has the logo as a transparent PNG image, but the page background is explicitly #fff. --Redrose64 🌹 (talk) 08:37, 28 July 2024 (UTC)[reply]

Quote from Branding guidelines: 2.1 Master logo // The master logo is red, white and blue, and should primarily be used on a white background. Also, a zip file with logos can be downloaded from UK Space Agency communications resources. —⁠andrybak (talk) 13:43, 28 July 2024 (UTC)[reply]

@Termynaytor: SVG files are comparatively easy to edit, especially when they were not created with InkScape. Use a plain text editor such as WordPad. This SVG image had just three elements - the <svg>...</svg> element itself, plus one <path /> element each for the red and blue portions. There is nothing to specify either background or transparency - SVG images are implicitly transparent, except for those areas where an object has been drawn that is 100% opaque.

I've added a fourth element, being <rect x="0" y="0" width="500" height="140" fill="white" stroke="none" /> which draws a white background before the coloured bits.

Are there any other SVG images that you need fixing? --Redrose64 🌹 (talk) 08:22, 28 July 2024 (UTC)[reply]

Thanks for that. There are other images in the thread linked by WOSlinker above such as the Porsche and Apple logos but people might prefer to keep the transparency in those cases. Termynaytor (talk) 08:42, 28 July 2024 (UTC)[reply]

A commons gadget that allows us to add a white background to images via a single button click would be really useful here... 🐸 Jdlrobson (talk) 21:52, 28 July 2024 (UTC)[reply]

@Jdlrobson: If I understand you correctly, you're suggesting a utility that, given the name of an existing image, will edit that image and save the amended image. My edit to File:UK Space Agency logo.svg wasn't difficult, but I don't think that it's something that could easily be automated in a way that fits all situations. --Redrose64 🌹 (talk) 22:20, 28 July 2024 (UTC)[reply]

That also may run afoul of c:COM:OVERWRITE, depending on specifics of the file, and the temptation of editors to use it widely on images of things that are not intrinsically "white background". DMacks (talk) 22:29, 28 July 2024 (UTC)[reply]

How to add a background color to an image in an infobox?

Moved from WP:Help Desk

– ~ 🦝 Shushugah (he/him • talk) 04:58, 30 July 2024 (UTC)[reply]

For example if a logo is all-white png it wouldn't be visible so a black background color is added to make it visible. Neocorelight (Talk) 03:24, 27 July 2024 (UTC)[reply]

You cannot rely on this because there is light and dark mode. Better to explicitly edit the image to have a background color. ~ 🦝 Shushugah (he/him • talk) 10:43, 27 July 2024 (UTC)[reply]

Wouldn't the color stay as is regardless of mode? Also please just answer the initial question. @Shushugah. Neocorelight (Talk) 23:16, 27 July 2024 (UTC)[reply]

I guess no one know how. Neocorelight (Talk) 23:38, 29 July 2024 (UTC)[reply]

Neocorelight, download the image and edit the background colour. Reupload the edited version to Wikimedia Commons, being sure to credit the original license holder, link to the version you remixed, and provide the same license as the original version.

If you don't have image editing software on your device, you can probably use the free online tool Photopea. Folly Mox (talk) 10:33, 30 July 2024 (UTC)[reply]

This has been fixed in Template:Infobox television with this edit that set the background to white (based on this discussion). Gonnym (talk) 13:03, 30 July 2024 (UTC)[reply]

Dark Mode doing strange things to Page History on pages where Pending Changes is active

Tracked in Phabricator
Task T369391

See https://en.wikipedia.org/w/index.php?title=Wikipedia:Articles_for_creation/Redirects&action=history

This page has WP:Pending changes activated. The edit history listing now looks odd when Dark mode is activated. On edits that have been accepted, that line has a white background instead of black/dark and the text is light-colored, making it more hard to read. Instead, this should be a dark grey background, lighter than the standard background, so as to fit with the dark scheme, and make the text readable.

-- 65.92.247.96 (talk) 07:01, 28 July 2024 (UTC)[reply]

Discussion at Template talk:Hidden archive top § Heading text colour unreadable in dark mode

You are invited to join the discussion at Template talk:Hidden archive top § Heading text colour unreadable in dark mode. Rummskartoffel 10:53, 28 July 2024 (UTC)[reply]

Cleanup from decades past

There's this recurring issue at Special:WantedCategories where a redlinked Category:Clean-up categories from YYYY gets generated because somebody has erroneously backdated a maintenance template to 15 or 20 years ago — following which a bot automatically recreates the resulting redlinked maintenance-queue category for that specific template, but then leaves the general "clean-up" container as a redlink that ends up becoming the category cleanup crew's job to fix.

For example, Category:Articles with unsourced statements from July 2004 has been recreated four times within the past two weeks, just from people accidentally typing 2004 instead of 2024 in a {{citation needed}} template somewhere in an article, which is obviously just a disruptive pain in the badonkadonk to have to keep dealing with over and over.

I've asked here before, and was told that it was possible, but obviously it didn't happen: is there any way that maintenance templates like {{citation needed}} can be made to do an ifexist check on categories, and file nonexisters in an error-catcher category (e.g. "citation needed with dating problems" or something along those lines) instead of causing the recreation of a redlinked category that's already been cleaned up and deleted in the past? Bearcat (talk) 13:21, 28 July 2024 (UTC)[reply]

Also, given that it's clearly possible for bots to detect and automatically create redlinked maintenance categories as needed, then can any of the following things that inevitably hit WantedCategories on a regular basis get farmed out to bots instead of becoming my job to fix?

"Wikipedia Today's featured article nominations from [Current Month and Year]", which consistently lands there at some point in the middle of every month without fail, and should really just be automatically created by a bot right off the top of the month if it's routinely expected to exist?
Any non-empty redlinks of the "Articles containing [Insert Language Here] text", "Pages with [Insert Language Here] IPA" and "CS1 [Insert Language Here]-language sources (lang code)" varieties?
Any non-empty redlinks for "Wikipedia sockpuppets of [User]" and "Suspected Wikipedia sockpuppets of [User]"? Bearcat (talk) 15:04, 28 July 2024 (UTC)[reply]

I'll comment on some of these.

Dated maintenance categories (such as Category:Articles with unsourced statements from July 2024) are created by AnomieBOT (talk · contribs) if either of two conditions apply: (i) it's now the last day of the preceding month; (ii) there's a page in the category and the date is valid - even if the year is a typo. I would expect that if you want different behaviour from AnomieBOT, your first contact should be Anomie (talk · contribs), who (unlike some botops I could name) is not only active but also replies to talk page messages.
Cats like Category:Wikipedia Today's featured article nominations from July 2024 have always been manual creations. One prolific creator (particularly of the early ones, in 2011-2016) was Bencherlite (talk · contribs), who is WP:MIA. Other people have also created them, see this list, but note that the person named is the one who made the last edit to the page, often this was the page creation but not always. I think that for this one, it's something to bring up at Wikipedia talk:Today's featured article/requests.
The sockpuppet ones should really be the responsibility of the WP:SPI admin or clerk who "tagged" the user pages.

HTH. --Redrose64 🌹 (talk) 17:18, 28 July 2024 (UTC)[reply]

Obviously sockpuppet ones should be the responsibility of the admin or clerk who tagged the page, but mistakes can and do happen — so there really needs to be a way to catch such mistakes before they become my problem to fix.

When it comes to the backdated maintenance templates, it's really a thing that the template needs to handle rather than the bot. The bot is just going to come along and create any non-empty redlink it finds, and can't easily modify a redlinked category to be different than what's there — it's the template that needs to be prevented from being able to generate a backdated redlink like that at all, so that there's nothing for the bot to have to recreate. So it's really that the template needs to have "if asked to regenerate outdated category that does not exist, then replace with problem-catcher category instead of redlinked date" code inside the template, because a bot can't make that happen if the template isn't already handling it. Bearcat (talk) 21:14, 28 July 2024 (UTC)[reply]

Some more details on how AnomieBOT works:

When the target category doesn't exist, the templates populate both Category:Articles with unsourced statements from July 2004 and Category:Articles with invalid date parameter in template. AnomieBOT looks through articles in the latter category to find the former, as there are simply too many possibilities for it to check for the former directly. Well, I suppose these days a DB query on Toolforge could be done, but suffix searches aren't very efficient.
AnomieBOT does look for missing "Clean-up categories from Month Year" categories to create them. I could have it also do "Clean-up categories from Year" if that's wanted. Would that be a special case, or should we have a Category:Wikipedia maintenance categories sorted by year to match Category:Wikipedia maintenance categories sorted by month?
AnomieBOT won't create dated categories for any date, only dates since 2004. I forget why I picked that year specifically, beyond deciding that anything earlier was definitely not some ancient article being undeleted or some ancient edit removing a maintenance tag being reverted. I could bump it to 2010 easily enough if people typing "200X" instead of "202X" is a common thing.
Having AnomieBOT create Category:Wikipedia Today's featured article nominations from July 2024-type cats wouldn't be quite as simple as most. Normally we'd just need to add the the base category to Category:Wikipedia categories sorted by month, but since in this case the base category is Category:Wikipedia Today's featured article nominations by month rather than Category:Wikipedia Today's featured article nominations I'd also need to configure an override for the bot. Also I'd need to do something if we don't want them to be created with {{Monthly maintenance category|cat=Category:Wikipedia Today's featured article nominations by month}}.
The non-date examples would need to be considered case by case. "Wikipedia sockpuppets of" and Wikipedia suspected sockpuppets of" seem like reasonable prefixes to search for. Not sure about "Articles containing", "Pages with", or "CS1".

HTH. Anomie ⚔ 00:10, 29 July 2024 (UTC)[reply]

Regarding bumping from 2004 to 2010 – can the bot look up the earliest existing month/year category and not create categories which are earlier than that? —⁠andrybak (talk) 15:00, 30 July 2024 (UTC)[reply]

Bad news: Category:Articles needing additional references from October 2006 is an active backlog. Good news: there are fewer than 1,000 articles in all of Category:Clean-up categories from 2006, not including those in Category:Articles containing potentially dated statements from 2006, which is apparently not a backlog category. – Jonesey95 (talk) 16:32, 30 July 2024 (UTC)[reply]

OK, so the cutoff year could be the earliest existing category's year or {{CURRENTYEAR}} − 10, whichever is the latest (the maximum out of the two). —⁠andrybak (talk) 18:00, 30 July 2024 (UTC)[reply]

I wonder how often people validly undelete, or unredirect, or otherwise revert to a revision that has a maintenance tag older than that. Or how often people change a tag from one category to another, suddenly populating the "another" category with a bunch of old dates. Also I'd rather have a consistent cutoff rather than having to try to look up an earliest date for every different category. Anomie ⚔ 23:47, 30 July 2024 (UTC)[reply]

Can I butt in here for a moment to ask if we're seriously considering making the lives of people who actually work the backlogged cleanup categories (I'm sure they exist) significantly harder, so that the people who keep Special:WantedCategories tidy are less inconvenienced? I've also had empty maint categories I've G6'd years ago pop back up, and that's a good thing, because it means someone's reverted an unsourced article that was made into a redirect years ago, or copy-pasted in an old version of a deleted article, or reverted a page to a really old version, and those all need to be dealt with. If we make the maintenance tags not categorize such edits, then they're going to be noticed by a lot fewer people. If it's just a matter of the bot not recreating redlinked grandfather cats, then have it make those. Or, y'know, deal with the underlying problem - most of the time the correct thing to do was a simple rollback or G4 speedy, in my experience - and then G6 the maintenance cat again. Even if you omit the last, it's not going to last an hour anyway; we've got admins who race each other for easy speedies like that. —Cryptic 03:56, 31 July 2024 (UTC)[reply]

Sections not collapsing on mobile

At Great Britain at the Olympics the sections are not collapsible as expected on the mobile interface. In my sandbox I tried removing sections until it worked again, then reinstating that section and removing everything else, only to find that it worked again. I also tried fixing the markup errors (specifically, invalid HTML attributes) but that didn't fix it either. So I can only assume the cause is the "Medals by sport" section just being excessively large. Is this a known limitation of the collapsing mechanism? Should that section be split up so the collapsing works? Hairy Dude (talk) 16:49, 28 July 2024 (UTC)[reply]

There's too many images on the page so the page cannot be mobile formatted (see mw:Recommendations_for_mobile_friendly_articles_on_Wikimedia_wikis ) 🐸 Jdlrobson (talk) 18:14, 28 July 2024 (UTC)[reply]

Image thumbs displaying in negative

The three linked "related articles" at the bottom of each article page are showing their thumbnails in photographic negative for me. A temporary glitch, a problem on my end (mobile android chrome), I don't know -- standard images in-article look fine. I wanted to let someone know in case there is an issue to fix. See, e.g., bottom of Thomas Cromwell or Wyatt's rebellion. Al Begamut (talk) 17:04, 28 July 2024 (UTC)[reply]

In dark mode or light? I can't reproduce the issue in either. Izno (talk) 17:58, 28 July 2024 (UTC)[reply]

This sounds like the behaviour of the dark mode gadget (rather than the WMF extension), which has always done this. Folly Mox (talk) 18:37, 28 July 2024 (UTC)[reply]

ah yes, that sounds like a possibility. thanks for helping me figure that out! Al Begamut (talk) 03:46, 29 July 2024 (UTC)[reply]

Query on template/category identification

So every once and a while I come across a composer with 3–4 works on Wikipedia, but no navigational template, so I go ahead and make one. Is there any way to generate a list of composers who are missing one still? Not sure if this is a bot-request matter, AWB request or something else entirely. (see parent cat)

So essentially, I'd be looking for categories like [[Category:Compositions by Example Person]] which have more than 2 pages, but there is no corresponding {{Example Person}} that exists. Aza24 (talk) 21:37, 28 July 2024 (UTC)[reply]

WP:RAQ would solve it I think. Izno (talk) 21:41, 28 July 2024 (UTC)[reply]

Awesome, thank you! Aza24 (talk) 22:31, 28 July 2024 (UTC)[reply]

Dark mode issues

In dark mode, at {{Stabbing Westward}}, the actual link for Stabbing Westward is an extremely dark grey that is difficult to see on a black background. Also, when editing, anything that is NOT a link is grey text on a white background. It was not this way before. Does anyone know how to fix this?

Grey text on white background when editing

Black text on black background when viewing

--Jax 0677 (talk) 22:10, 28 July 2024 (UTC)[reply]

This is a known issue for visited links in navbox titles. There is a proposed fix. – Jonesey95 (talk) 22:31, 28 July 2024 (UTC)[reply]

Reply - Good to know. Can't wait to hear more about it. --Jax 0677 (talk) 22:54, 28 July 2024 (UTC)[reply]

I don't edit templates, generally, but even when I edit regular pages after hours (when the site changes colours), I now have that white edit window with light-coloured text, rendering everything essentially unreadable. I've been eschewing editing when the site is dark (or, like right now, typing in a plain-text program and copying/pasting), thinking surely this is a widespread problem and will be fixed quickly, but maybe it's only tied to what you're discussing, here? You linked to a discussion about templates and navboxes; will that proposed fix also affect all white-background editing issues, too? — Fourthords | =Λ= | 02:27, 1 August 2024 (UTC)[reply]

Issue with transclusion of project subpages

On Wikipedia:WikiProject Athletics, the subpages /leftpanel, /rightpanel, and /Members are supposed to be transcluded, but since recently they are shown as links. As far as I can tell, there were not any recent changes made to this project page or its subpages that could have triggered this. The issue with /leftpanel was reported on the project talk page on 28 July. Anyone know what caused it or how it could be fixed? – Editør (talk) 08:40, 29 July 2024 (UTC)[reply]

Editør, the page is in Category:Pages where post-expand include size is exceeded. — Qwerfjkl talk 08:54, 29 July 2024 (UTC)[reply]

Thank you, I'm assuming this identifies the cause. I'm not sure how to fix this though. – Editør (talk) 09:09, 29 July 2024 (UTC)[reply]

Editør, I assume you'd need to simplify or remove some of these template calls:

Transclusion expansion time report (%,ms,calls,template)
100.00% 1838 242      1 -total
 37.90%  696 694      1 Wikipedia:WikiProject_Athletics/rightpanel
 28.63%  526 307      1 Wikipedia:WikiProject_Athletics/leftpanel
 23.79%  437 326      1 Template:Scrolling_window
 21.97%  403 905      1 User:AlexNewArtBot/AthleticsSearchResult
 19.57%  359 777      1 Wikipedia:Version_1.0_Editorial_Team/Athletics_articles_by_quality_statistics
 19.35%  355 777      1 User:WP_1.0_bot/Tables/Project/Athletics
 16.46%  302 510     15 User:AlexNewArtBot/MaintDisplay
 14.55%  267 473    196 Template:Pagelinks
 14.43%  265 233      1 User:WP_1.0_bot/WikiWork

— Qwerfjkl talk 09:32, 29 July 2024 (UTC)[reply]

Thank you for the additional info. I don't think I understand enough about the issue to be able to fix this myself. – Editør (talk) 09:39, 29 July 2024 (UTC)[reply]

The expansion limit is broken by {{scrolling window|link=User:AlexNewArtBot/AthleticsSearchResult|height=700px|title=New articles}} in Wikipedia:WikiProject Athletics/leftpanel. The transcluded content is passed multiple times and the size is added each time. If the code is replaced with a link to User:AlexNewArtBot/AthleticsSearchResult then Wikipedia:WikiProject Athletics will go from breaking the 2 MB limit to only using 7% of it. PrimeHunter (talk) 09:56, 29 July 2024 (UTC)[reply]

When I changed it to {{User:AlexNewArtBot/AthleticsSearchResult}} and purged the project page's cache, the transcluded content of /leftpanel was displayed again, so part of the issue seems to be caused by {{scrolling window}} making the project page exceed some limit as you indicated. I'm not sure why this happened now, maybe because there the transcluded contents were much longer than usual due to the Summer Olympics? I have reverted my edit, because the project page became too long without the scrolling window. However, the change and purge didn't fix the transclusion issue for /rightpanel and /Members. – Editør (talk) 10:53, 29 July 2024 (UTC)[reply]

My suggested fix was a link to User:AlexNewArtBot/AthleticsSearchResult, meaning [[User:AlexNewArtBot/AthleticsSearchResult]] without transclusion. If you want it transcluded and scrolling then you can place this directly somewhere in Wikipedia:WikiProject Athletics:

<div style="font-size: 90%;   height: 700px; border: 1px solid gray; overflow: auto; padding: 0.5em 1em; " title="New articles">
{{User:AlexNewArtBot/AthleticsSearchResult}}
</div>

PrimeHunter (talk) 11:13, 29 July 2024 (UTC)[reply]

The suggested solution with a div and CSS didn't work, I'm not sure why not. It even removed additional transcluded content from the project page, so I have reverted my edits for this. – Editør (talk) 11:40, 29 July 2024 (UTC)[reply]

You added it to Wikipedia:WikiProject Athletics/leftpanel where it get's a transclusion copy in Wikipedia:WikiProject Athletics and breaks the limit. That's why I suggested to place it directly in Wikipedia:WikiProject Athletics, meaning by editing that page after removing the transclusion from Wikipedia:WikiProject Athletics/leftpanel. It will work but you may have to fiddle with the page to place it nicely. PrimeHunter (talk) 12:02, 29 July 2024 (UTC)[reply]

Ah I see, I missed that you meant direct in the project page. I'm afraid don't have time for the fiddling right now. – Editør (talk) 12:07, 29 July 2024 (UTC)[reply]

I have implemented my original suggestion to just link User:AlexNewArtBot/AthleticsSearchResult.[4] Wikipedia:WikiProject Athletics now displays correctly and only uses 7% of the transclusion limit. PrimeHunter (talk) 12:21, 29 July 2024 (UTC)[reply]

Thank you! – Editør (talk) 13:10, 29 July 2024 (UTC)[reply]

Adding Redirect Cat Causes Double Redirect

Where do I report an error in trying to add a redirect category to an existing redirect using the Tag button?

I tried to add the {{R with possibilities}} tag to a redirect, and it created a second empty redirect shell. The original redirect had been Special:Permalink/1210632744. When I tried to add the additional category, using the Tag button, it applied this diff: Special:Diff/1237443069. As can be seen, it moved the existing redirects into a new shell, leaving an empty shell.

I have corrected it, but this is a bug.

If I should report this somewhere else, where? Robert McClenon (talk) 21:02, 29 July 2024 (UTC)[reply]

WP:Twinkle says to report bugs "on the talk page, or directly at our GitHub". —Cryptic 21:09, 29 July 2024 (UTC)[reply]

I suspect that TW doesn't recognise the template redir {{r cs}}. The page Benjamin Howard (filmmaker) has been deleted, but admins may view the problem diff here. --Redrose64 🌹 (talk) 21:54, 29 July 2024 (UTC)[reply]

Tech News: 2024-31

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Feature news

Editors using the Visual Editor in languages that use non-Latin characters for numbers, such as Hindi, Manipuri and Eastern Arabic, may notice some changes in the formatting of reference numbers. This is a side effect of preparing a new sub-referencing feature, and will also allow fixing some general numbering issues in Visual Editor. If you notice any related problems on your wiki, please share details at the project talkpage.

Bugs status

Some logged-in editors were briefly unable to edit or load pages last week. These errors were mainly due to the addition of new linter rules which led to caching problems. Fixes have been applied and investigations are continuing.
Editors can use the IP Information tool to get information about IP addresses. This tool is available as a Beta Feature in your preferences. The tool was not available for a few days last week, but is now working again. Thank you to Shizhao for filing the bug report. You can read about that, and 28 other community-submitted tasks that were resolved last week.

Project updates

There are new features and improvements to Phabricator from the Release Engineering and Collaboration Services teams, and some volunteers, including: the search systems, the new task creation system, the login systems, the translation setup which has resulted in support for more languages (thanks to Pppery), and fixes for many edge-case errors. You can read details about these and other improvements in this summary.
There is an update on the Charts project. The team has decided which visualization library to use, which chart types to start focusing on, and where to store chart definitions.
One new wiki has been created: a Wikivoyage in Czech (voy:cs:) [5]

Learn more

There is a new Wikimedia Foundation data center in São Paulo, Brazil which helps to reduce load times.
There is new user research on problems with the process of uploading images.
Commons Impact Metrics are now available via data dumps and API.
The latest quarterly Technical Community Newsletter is now available.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 23:08, 29 July 2024 (UTC)[reply]

Page not appearing in search

Hi there, I was directed here after asking this question at the Teahouse. Roger Uren is a page I created for a former diplomat that was investigated by Australian intelligence services for alleged espionage. I told a friend to look it up, they searched for it in google as "Roger Uren Wikipedia". His page didn't pop up, but all mentions of him on other Wikipedia pages did. The Roger Uren page was created in early April (over 90 days ago). Is there any reason why it wouldn't appear? Another user told me that the Wikipedia page appears in a basic search of his name, but disappears when you add "Wikipedia" to the search. 30Four (talk) 05:04, 30 July 2024 (UTC)[reply]

Probably a side effect of our logic that blocks the article from indexing when it is newly created. When this index'ing restriction is lifted, Google isn't as likely to pick up the article until someone looks for it, edits it, or links to it from outside of wikipedia. It seems to show up now however. —TheDJ (talk • contribs) 08:33, 30 July 2024 (UTC)[reply]

If you were literally searching Google for "Roger Uren Wikipedia" it would be less likely to appear, as those 3 words aren't together. This page is the number one result when I search for "Roger Uren" site:wikipedia.org, so Google certainly knows about it. The page was also recently patrolled an hour or so ago (see Special:Redirect/logid/163473907), so that may help. — xaosflux ^Talk 09:53, 30 July 2024 (UTC)[reply]

The table of contents behavior has changed, some time in the last few hours. I'm using Firefox on a Windows PC. Until now the table of contents has displayed on the left sidebar, which is what I want. Now I still see that when displaying Firefox full screen, but when it's not full screen, which is my usual way of working, I don't see the TOC. I can still get there by clicking the TOC icon in the upper left, or by expanding Firefox to full screen, but I strongly prefer the previous behavior. What has changed, and can it be set back to the way it was? (Note that I've not switched the TOC to "hide", it's still in "move to sidebar" mode.) — Mudwater^(Talk) 10:26, 30 July 2024 (UTC)[reply]

It depends on the width of your screen. Maybe you don't have the exact window width ? Or possibly you zoomed in the browser one nudge with the zoom function that a browser has ? —TheDJ (talk • contribs) 11:53, 30 July 2024 (UTC)[reply]

Okay, I think I see what happened. I didn't realize this, but the width that I usually use for the browser window is slightly larger than the minimum for displaying the table of contents in the left sidebar. Then today, without noticing it, I was using a slightly narrower window for the browser, causing the TOC to mysteriously disappear. When I widen the window by a small amount, the "problem" is fixed. Thanks for your help. — Mudwater^(Talk) 12:08, 30 July 2024 (UTC)[reply]

Mark all revisions as patrolled

On Wikispecies (where I am an admin), if I view the history of a page with multiple unpatrolled edits, I see an option to "Mark all revisions as patrolled". I do not see this here on en.Wikipedia, nor on Wikidata.

How can I enable this on the latter projects (where I am not an admin; if that is relevant)?

I searched for that string, and found only one discussion, from 2009, which refers to an "Enchanted [SIC: enhanced?] recent changes" option under preferences -> Recent changes, but I see no such option on any of the listed projects. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:20, 30 July 2024 (UTC)[reply]

You are incorporating meta:MediaWiki:Gadget-patrolRevisions.js via a gadget loader in to your global user script file meta:User:Pigsonthewing/global.js. — xaosflux ^Talk 19:14, 30 July 2024 (UTC)[reply]

It requires the patrol right. At the English Wikipedia that means administrator or new page reviewer. You're the latter so I don't know why the link is missing. I tried loading the script in meta:User:PrimeHunter/global.js. My admin account shows "Mark all revisions as patrolled" after clicking one of the "hist" links at Special:NewPagesFeed. PrimeHunter (talk) 21:37, 30 July 2024 (UTC)[reply]

Small font?

Can anyone decipher why the font on the entire article is small at 2024 Venezuelan presidential election? Or is it just my eyes? SandyGeorgia (Talk) 02:40, 31 July 2024 (UTC)[reply]

Weird, but it seems that when the page first loads, the font size looks normal, but then it resets itself smaller. SandyGeorgia (Talk) 02:42, 31 July 2024 (UTC)[reply]

Have you tried resetting the zoom of your browser to original ? —TheDJ (talk • contribs) 07:12, 31 July 2024 (UTC)[reply]

Thanks, but I don't have a small font on other articles. SandyGeorgia (Talk) 13:48, 31 July 2024 (UTC)[reply]

@SandyGeorgia: With some browsers, the zoom setting is remembered in a non-intuitive way. For example, if you zoom out on one page, click through to another page, the zoom level is inherited; if on that you reset to normal zoom then return to the first page, it may be normal, or it may still be zoomed out. --Redrose64 🌹 (talk) 21:46, 31 July 2024 (UTC)[reply]

Thanks ... now if I can figure out how to reset iPad <sigh> ... SandyGeorgia (Talk) 15:22, 1 August 2024 (UTC)[reply]

black list

could someone create rd's from Ɖ𝼅 and D𝼅 to Voiced retroflex lateral affricate, parallel to the other articles on affricates?

thanks, — kwami (talk) 09:27, 31 July 2024 (UTC)[reply]

Kwamikagami, you can create them, because you have the template editor perm. — Qwerfjkl talk 09:38, 31 July 2024 (UTC)[reply]

Oh yeah. Thanks! — kwami (talk) 10:02, 31 July 2024 (UTC)[reply]

Inflation template broken

I noticed on Hey Jude#Auctioned lyrics and memorabilia that the inflation conversion from pounds to US$ is showing "US$FXConvert/Wordify error: cannot parse value 'Unknown country code for year 2023: GBR '". Many of the GBR test cases on Template:FXConvert/testcases are similarly broken, so it's probably affecting a lot of articles. I can't tell where exactly this data is coming from or if there were recent changes causing this. hinnk (talk) 19:00, 31 July 2024 (UTC)[reply]

At a quick glance, it looks like data for {{Inflation}} in Template:Inflation/UK-GDP/dataset, Template:Inflation/year, and Template:Inflation/fn was updated for 2023, but Template:To USD/data/2023 was not updated. {{FXConvert}} seems to assume that will have been updated too. BTW, I see similar errors for CAN, IND, and BGD. Anomie ⚔ 21:20, 31 July 2024 (UTC)[reply]

@Snowman304: @Izno: Would the changes mentioned in Template talk:Inflation#Template-protected edit request on 15 July 2024 have caused this? hinnk (talk) 22:41, 31 July 2024 (UTC)[reply]

What Anomie is saying there is that FXConvert was already broken. The changes there just made it clear that it is. Izno (talk) 23:09, 31 July 2024 (UTC)[reply]

Oh my mistake, I had read it as the template working (or at least, not showing any errors) until the new data exposed a case it couldn't handle. Is there a more appropriate place to raise this issue then? I notice Template:FXConvert doesn't have a talk page. hinnk (talk) 23:58, 31 July 2024 (UTC)[reply]

There are many errors at {{FXConvert/doc}} and that template's testcases page. It looks like the error is generated by {{To USD/data/2023}}, which is much smaller than {{To USD/data/2021}}. It appears that if a country code is missing from the "/2023" template, it generates an error message. It is unclear to me how numbers are chosen for the /2023 template. – Jonesey95 (talk) 04:49, 1 August 2024 (UTC)[reply]

suppressing a Help talk: warning/notice

Recently and editor asked a question at WP:HD. I replied that the correct place to have asked that question was Help talk:Citation Style 1. In response, the editor said that they didn't because there is a notice that reads:

Attention

Talk pages in this namespace are generally not watched by many users. Please consider visiting the Help desk for a more prompt response or reviewing the Help contents for quick tips.

That message is displayed when the editor is seeing the edit view. Is there any way to suppress that warning/notice for a single Help talk: page?

—Trappist the monk (talk) 13:55, 1 August 2024 (UTC)[reply]

Trappist the monk, presumably that would require some edit to Template:Editnotices/Namespace/Help talk. — Qwerfjkl talk 14:02, 1 August 2024 (UTC)[reply]

Which would/could impact many/most/all talk pages that display that notice. I want to suppress the notice only at Help talk:Citation Style 1.

—Trappist the monk (talk) 14:14, 1 August 2024 (UTC)[reply]

I'm assuming you want to suppress it for others here, not just for yourself? — xaosflux ^Talk 14:16, 1 August 2024 (UTC)[reply]

Yes. I don't want editors to be scared away from the talk page where they can get cs1|2 help. All of the cs1|2 template and module talk pages redirect to Help talk: Citation Style 1. Editors should not arrive there and then think that they must go to some other page for help. If we wanted editors to ask questions at WP:HD, we'd have redirected the cs1|2 template and module talk pages there.

—Trappist the monk (talk) 14:42, 1 August 2024 (UTC)[reply]

Assuming the user story is "I should post my question somewhere besides here because of that notice" - perhaps that could be overcome by adding more to Template:Editnotices/Page/Help talk:Citation Style 1 (the notice for only that page) stating that unlike most HT: pages, questions are most welcome here. — xaosflux ^Talk 14:18, 1 August 2024 (UTC)[reply]

Can editnotices have conditionals in them? Gonnym (talk) 14:31, 1 August 2024 (UTC)[reply]

Yes, they can. Anomie ⚔ 14:44, 1 August 2024 (UTC)[reply]

You assume correctly. I'm not convinced that conflicting messages are ever a good thing. Is it possible to create a template that does nothing but drag in a templatestyles css page that contains something like:

.visibility {
  display: none !important;
}

—Trappist the monk (talk) 14:42, 1 August 2024 (UTC)[reply]

It looks like that should almost work, and work from the page-specific edit notice, but .visibility looks like it wouldn't be correct (also the !important should be unnecessary). As things are you'd want to target #Visibility, although personally I'd probably do .editnotice-namespace #Visibility just in case. Anomie ⚔ 14:52, 1 August 2024 (UTC)[reply]

And that works. Thank you. See {{suppress visibility notice}}.

—Trappist the monk (talk) 15:36, 1 August 2024 (UTC)[reply]

@Trappist the monk You could wrap the editnotice (or the "help" line in {{Visibility}}) in {{#ifeq:{{ROOTPAGENAME}}|Citation Style 1||...}} as long as there's only one (or a small handful) of pages that need to be excluded. --Ahecht (TALK
PAGE) 14:33, 1 August 2024 (UTC)[reply]

Yeah, that would probably work. But, but, I hate special cases ...

—Trappist the monk (talk) 14:42, 1 August 2024 (UTC)[reply]

SVG dark-mode support

It should be possible to specify the colour-scheme to be used when rasterising SVG files. This would influence the default styling applied to SVG elements and activate any CSS media queries that target prefers-color-scheme. For example, a background normally rendered as pale blue for white backgrounds might select a darker shade in night-mode to avoid the garish contrast:

:root {
	color-scheme: light dark;
	fill: #00c;
}
@media (prefers-color-scheme: dark){
	:root { fill: #003; }
}

The MediaWiki thumbnail generator already provides a means of specifying language when rendering multilingual SVGs by prefixing the thumbnail's filename with langid- (where id is the BCP 47 tag of the desired language). The same approach could be used to request a rendering of an SVG using a particular colour-scheme; for example, by supporting an optional dark- prefix in thumbnail URLs. Expressed in BNF, the format of thumbnail URLs would be:

<thumbnail-url> ::= <base> "/" <name> "/" [<theme>] [<lang>] <size> "-" <name> ".png"
<base>          ::= "https://upload.wikimedia.org/wikipedia/commons/thumb/1/14/"
<theme>         ::= "dark-" | "light-"
<lang>          ::= "lang" <locale> "-"
<size>          ::= <width> "px-"

; Variables (values shown here by way of example)
<name>          ::= "Lang_Status_01-EX.svg"
<locale>        ::= "de"
<width>         ::= "480"

I'm aware of a CSS class named .skin-invert-image that inverts image colours for dark-mode users, but it's an inelegant and hacky solution that really only works for images with simple colour palettes (like this). A more robust and seamless approach would be to extend the image syntax to include a new parameter named theme that recognises one of three values: dark, light, and auto (the default). Auto would select either the dark or light rendering of an SVG based on the reader's display preferences, while dark or light specify motifs unconditionally (potentially facilitating the use of <picture> tags, should MediaWiki support them in the future).
— Alhadis (talk) 23:07, 1 August 2024 (UTC)[reply]

Latest revision as of 06:13, 2 August 2024

Adding documentation subpage to module doc pages

Display of Text Image is Distorted

dark mode on Wikipedia

dark text on a light background in dark mode

light text on a light background in dark mode

dark mode on laptop

Start a discussion notice on Talk pages

List of cities proper by population density

Table covers appearance settings

Removing the need for round robin moves

Dark mode images with transparent color

How to add a background color to an image in an infobox?

Dark Mode doing strange things to Page History on pages where Pending Changes is active

Discussion at Template talk:Hidden archive top § Heading text colour unreadable in dark mode

Cleanup from decades past

Sections not collapsing on mobile

Image thumbs displaying in negative

Query on template/category identification

Dark mode issues

Issue with transclusion of project subpages

Adding Redirect Cat Causes Double Redirect

Tech News: 2024-31

Page not appearing in search

Table of contents

Mark all revisions as patrolled

Small font?

black list

Inflation template broken

suppressing a Help talk: warning/notice

SVG dark-mode support