Talk:Reading/Web

Discussions: Desktop Improvements • Accessibility for reading.

---

You can comment in any language. We are especially interested in:

• Feedback on the functionalities we have already deployed.

• Expanding the list of existing gadgets and user scripts that are related to providing a better desktop experience.

We are discussing with many volunteers and communities at the same time. It may take some time for us to reply here. We apologize for that.

Thank you!

(Translate this page)

Page previews

Page Previews feature needs a rethink.

Please disable page previews for logged-out users by default. Showing pop-ups on hover actually breaks "accessibility" for normal people when it is unintended. There are certain natural semantics attached with the use of mouse pointer. Causing pop-ups on hover is like causing a click on the links every time the mouse pointer hovers over them. —2401:4900:1B1B:6E30:494C:49BD:104F:56FB 15:54, 12 April 2023 (UTC)

Thank you for this comment. I'll inform the team about your idea. Soon, we'll be asking volunteers to share their opinions on the Foundation's annual plan. Announcements will be sent across the wikis and other community communication channels. You're welcome to join that discussion, too! SGrabarczuk (WMF) (talk) 15:05, 13 April 2023 (UTC)

I like the previews but I would like to customize the size of them. How is this possible? Is there a html or css panel somewhere? --S4a4 (talk) 10:03, 6 June 2025 (UTC)

Bug with Haiti's page preview

I am not sure if this is the place to report bugs, but the page preview for Haiti's wikipedia page seems to display its coordinates instead of the lead section. It may be an issue with the article instead of Page Previews, but I am just guessing.

Some of technical info (if needed)- I am on a laptop (16:9, 1080p); using the latest version of Firefox, although the preview didn't work on Google Chrome and MS Edge as well. I haven't checked if the bug is present on other devices. Bluejet007 (talk) 11:59, 7 June 2023 (UTC)

Hi @Bluejet007, thanks for writing here. What do you mean by "display its coordinates instead of the lead section"? Could you provide a screenshot perhaps? If you add ?safemode=1 to the URL, does the issue exist, too? SGrabarczuk (WMF) (talk) 21:05, 13 June 2023 (UTC)

The issue was with the article not following MOS:ORDER. It has been fixed by another editor and the preview is now functioning. I would consider this issue closed. In case you still want to know how the preview looked before the fix, it was a blank preview without an image and the article text. Only the coordinate values were displayed in simple text formatting.

Also, the preview for a Regional Meteorological Centre in India doesn't display its text (screenshot in my sandbox), but I think it is again an issue with the page rather than with the gadget.

PS If I made any minor mistakes, please bring it up. I am still learning how edit and contribute. Bluejet007 (talk) 04:42, 14 June 2023 (UTC)

@SGrabarczuk (WMF): . See en:User talk:DB1729#Coords. Moving the coords to the bottom per MOS:ORDER is apparently not a valid fix. For an example, go to English WP and hover over the link to Rosario Strait and it displays "There was an issue displaying this preview" instead of giving the preview. It has been suggested to me that I report this behavior as a bug. --DB1729 (talk) 00:29, 22 June 2023 (UTC)

Use AMP as default

I have a question about advanced mobile contributions: are there plans to make AMP the default option for mobile web soon? And if not, would it be possible to make it default on select projects per community consensus? We get more and more questions about missing features in mobile web on dewiki and I keep pointing users at AMP. Many people are not even aware of the option. I believe it would be really useful to have it enabled as default (at least for registered users, but I would also recommend it for unregistered ones). XanonymusX (talk) 08:05, 19 June 2023 (UTC)

Please prevent a bug were we get automatically switched to advanced mode when editing or viewing

Any fix to this would be greatly appreciated. I'm tired of having to see the message saying "Please reload the page to enable hotcat", which I never wanted to enable. 2601:206:8580:6F10:25DA:8BB8:2738:3C9C 23:10, 20 June 2023 (UTC)

Unification/standardization problem

Tracked in Phabricator
Task T341133

Some sister projects usually do not use coordinates, so the presence of a button Nearby in mobile site (press ☰) is not clear. [1][2] [3] Proeksad (talk) 21:53, 26 June 2023 (UTC)

Thank you @Proeksad for telling us about this problem. I've filed a Phabricator task. Now, we need to wait for decisions who and when would be working on it. SGrabarczuk (WMF) (talk) 13:36, 5 July 2023 (UTC)

 Comment: The same feature is in Wikispecies and non-content wikis such as .wikimedia.org (meta., foundation., fi., pt., ru., wikimania., ...) But I don't know enough about all these wikis. Perhaps this is maybe usefull for testing Proeksad (talk) 20:32, 5 July 2023 (UTC)

Great, issue resolved! Proeksad (talk) 20:25, 6 July 2023 (UTC)

Talk:Reading/Web/Advanced mobile contributions

Hi. I need help, because the mentioned page is restricted to edit.

In English wikipedia mobile version, the "Advanced mode" keeps enabling automatically after some recent updates, and it gives some annoying features which I do not want currently.

Please stop it, one should enable it themselve if they want. It shouldn't turn on automatically, just like it was few days back. Hope for your kind response please, thank you! M.Billoo2000 (talk) 18:00, 1 July 2023 (UTC)

Hello @M.Billoo2000, thanks for coming here to write about those issues. We’ll discuss them, and I’ll let you know what the next steps would be. SGrabarczuk (WMF) (talk) 13:24, 5 July 2023 (UTC)

Enable globale settings for Special:MobileOptions

Tracked in Phabricator
Task T233802

Hi @SGrabarczuk (WMF) I've raised this question a couple of months ago and noticed it got archived unanswered [4]:

Is it possible to add an option to Special:GlobalPreferences and/or Special:MobileOptions to enable advanced mode globally?

As a global sysop I'm fighting crosswiki spam/vandalism across many wikis using both mobile and desktop devices. It's very annoying that I need to enable the advance mode for every project individually instead of having the option to enable it globally. Thanks! Johannnes89 (talk) 16:03, 4 August 2023 (UTC)

Hello @Johannnes89! I'm happy to give you the answer. The rationale for this change has been known, and personally, I do see clearly who would benefit and why. You may take a look at the Phabricator task to see discussions we've had about it.

Unfortunately, it's not in our plans to add this option. This year, our team is focusing on building something like preferences for logged-out users, dark mode, and readability.

I wholeheartedly encourage you to put this idea into Community Wishlist Survey/Sandbox, though. If this idea is submitted and supported by more people (it doesn't need to be at the top of the charts) we will be more likely to do this. Granting Community Wishlist Survey wishes is becoming a shared effort across the technical teams of the Foundation. So, 🤞! SGrabarczuk (WMF) (talk) 18:38, 4 August 2023 (UTC)

Thanks, I'll keep this in mind for next years Community Wishlist Survey! :) Johannnes89 (talk) 18:43, 4 August 2023 (UTC)

Adding "simple english"option before beginning of an article

The true power of Wikipedia, I think, in its delivery of knowledge. Simple English Wikipedia will open more Avenue for people to learn things with plain language and it also allow the simple English Wikipedia to expand in usage and development. The "open in simple English Wikipedia "link can be placed at the top so that people can choose to read in plain language. When more attention is given to this very underrated project, I suppose many more people will take part in creating more articles. Also, simple English Wikipedia allows access of knowledge to people with learning difficulties and intellectual disability. Kaveinthran (talk) 08:17, 27 August 2023 (UTC)

Hi and thanks for this idea, @Kaveinthran. If I understand correctly, this is a proposal for a new project. Although it seems to be a small and therefore easy task, I doubt if we could spend any time on it, unfortunately. This is because we work on projects where all the wikis may benefit, like Desktop Improvements or Accessibility for reading. I guess that in the meantime, English Wikipedians might write a gadget addressing this.

It is possible that at some point, we'll make a similar change on all the wikis. We were thinking on allowing a one-click access to one or two language versions, but it will most likely depend on the user preferences and behavior (like recently read wikis), not on the hard wiki-wide settings, so the impact on Simple English Wikipedia would be smaller than the one you're hoping for.

Thanks, SGrabarczuk (WMF) (talk) 13:06, 28 August 2023 (UTC)

Issue with State-sponsored terrorism Wikipedia page

The page preview for the Wikipedia page State-sponsored terrorism shows some sort of gory surgery picture as the page preview. Looking through the page, I don't see the image in question and as such I don't know why the image shows up in the page preview. Can anyone explain why this is, or otherwise fix it? Thanks! --Paulie 27 (talk) 14:29, 7 September 2023 (UTC)

Hey @Paulie 27, thanks for letting me know. It was because of a vandalism on a template used in that page. Now it should be gone, and if the image is visible, this is because of cache. It will be gone soon anyway. SGrabarczuk (WMF) (talk) 16:23, 7 September 2023 (UTC)

Page preview for Mosque article showing unrelated country flag

Hi, an editor noticed that the page previews for Mosque and Waqf (and perhaps others we haven't noticed) are currently showing an Israeli country flag, which has no relation to the articles in question (example screenshot here; see talk page discussion here). As far as we can see, the flag isn't used in the articles or in their Wikidata items, etc, so I'm wondering if anyone here has an idea of where this is coming from? (We haven't tried overriding it by adding lead images to the articles, I figured it would be good to know what's causing this first.) Thanks for any help, R Prazeres (talk) 22:19, 16 September 2023 (UTC)

Update: I believe the cause has been identified at the talk page and this has been resolved ([5]). Thanks. R Prazeres (talk) 06:41, 17 September 2023 (UTC)

Page Previews show cached vandalised pages

I recently came across a link to https://en.wikipedia.org/wiki/Triple_Entente on wikipedia, which instead of correctly displaying a preview to the page, simply read "Is fortnite addiction real?". This line was part of vandalism on the Triple Entente page, which had since been reverted, but apparently the vandalised version remained cached, which lead to it being the version displayed as a preview. After I forced a cache purge of the page this issue appears to be solved, but may appear after other cases of vandalism, on other articles as well. I suggest automatically purging the cache of a page after reverting changes on that page. Abakesh (talk) 15:57, 15 January 2024 (UTC)

Vector 2022 vote in Russian Wikipedia

Dear @OVasileva (WMF), @NBaca-WMF, @Jon (WMF), @JScherer-WMF and @SGrabarczuk (WMF), you announced your plans to deploy Vector 2022 by default in Russian Wikipedia by 13th of February. There was a lot of discontent about this allegedly premature deployment, so I organized a vote on the question whether the community supports it at the current moment. Only 6% of the community members think that Vector 2022 is ready to be used by default, while 94% of users prefer the deployment to be postponed until the diverse problems with Vector 2022 are solved. Please take this into consideration and answer about it here or in the original topic. Wikisaurus (talk) 15:26, 11 February 2024 (UTC)

I would add a bit to let you understand our community members' point of view.

From our perspective, an effective way of implementing such major changes would require several iterations, starting from effective and wide top-down information campaign regarding your plans; gathering the feedback; reporting on the measures taken and proceeding to the next iteration until everyone is ready. What happened instead.

1. You tried to collect some feedback of the user experience with the Vector 2022 by creating a topic inside our forum. It was a good step but you failed to reach the wide audience; the vast majority of the community simply missed it. As a result, lots of people still experience problems with Vector 2022 and have bugs to report but have no idea what to do with them, how to report them. What could be done better is to send an email to everyone or put a banner on the main page in order to really reach as many members as possible. It's not an overkill in case when you plan to change the whole UI.
2. When a message with feedback request was posted, you didn't provide the context of this. It wasn't mentioned that this topic was the last chance to post a bug and that the next step will be the immediate switching to the Vector 2022 by default. It didn't sound very important, it looked more like some routine topic; so many if not most readers ignored it. You could have warned everyone about the big picture.
3. The feedback wasn't processed properly. There were some issues described by the community members, but they we were left in the discussions and never made it to the Phabricator. I spent time to scroll through everything and re-post some of them to the Phabricator by myself but what if I didn't? You could either process it carefully by yourself or post a detailed instruction on how our community members can post bugs to Phabricator by themselves, or both.
4. As I checked, almost half of the Russian audience has a screen resolution of 1280x1024 or less which is fine for the old UI but absolutely not enough for the Vector 2022. There is a dozen of serious issues in the user experience with Vector 2022 with such a resolution. Some elements overlap, some elements become confusing after scrolling; there are double vertical scroll bars; UX on the tablets became worse etc. You should not switch to Vector 2022 before these issues are solved.
5. There are thousands of Russian articles with wide tables and wide images, panoramas and other wide objects that looked fine in the old UI but the layout will break the UX in Vector 2022. What you could do is provide tools to identify these pages, provide us with the guideline on how to adapt them beforehand, give us time to inform the article watchers and implement these changes, then collect feedback and THEN proceed with the switching.
6. The last post of your team with the final switch date on short notice caught people (especially active editors) unprepared. They still have issues with Vector 2022 and see no interest from your side to fix it. They feel that you don't care about them as there was no mention from your side that they can influence your decision. There is tension and mistrust growing. Another reason why it happens is that there already were precedents of actions taken by the WMF without reaching consensus with the community. The common voice is now "WMF ignored us before, now they ignore us again". Members feel powerless and rightless, and frustrated. What you could do is demonstrate that their voice is heard and that it's important; instruct them on how to reach you and demonstrate that you are willing and able to take action, that you will react on that voice.

Nikolay Komarov (talk) 08:55, 12 February 2024 (UTC)

Yes, thanks for this detailed report, I support it. Examples of incorrect operation can be seen at the link & here. Lesless (talk) 13:46, 12 February 2024 (UTC)

Modo escuro na Wikipédia em português

@Quiddity (WMF): Olá! A opção "modo escuro" está em inglês na Wikipédia em português. Cosmo Skerry (talk) 19:53, 30 April 2024 (UTC)

Thank you for this bug-report. I've told the team that is working on this feature. They are investigating a possible cause. Quiddity (WMF) (talk) 21:01, 30 April 2024 (UTC)

@Cosmo Skerry - thanks for your report! Just to confirm - you are referring to the dark mode on the mobile website. Is that right? OVasileva (WMF) (talk) 07:32, 1 May 2024 (UTC)

@OVasileva (WMF): yes, that's correct! Cosmo Skerry (talk) 12:21, 1 May 2024 (UTC)

"Herunterladen als PDF" (Download as PDF) doesn't work

When trying to get the PDF file from URL "https://de.wikipedia.org/wiki/EN_IEC_81346" it returns an error: "Buch-Rendering fehlgeschlagen" and the explaining text is even more confusing: "Einzelne Seiten herunterladen Der Buchgenerator unterstützt kein PDF-Rendering (Details), aber du kannst für einzelne Artikel „Herunterladen als PDF“ aus den Werkzeugen in der Seitenleiste ausprobieren ."

Actually that Download is what I wanted to do. 4inHand (talk) 04:31, 16 July 2024 (UTC)

@4inHand: Hello, you can download the pdf file by using this link. SCP-2000 (talk) 15:08, 22 July 2024 (UTC)

And maybe it related to this recent ticket phab:T368900? cc dewiki interface admin Hgzh. SCP-2000 (talk) 15:19, 22 July 2024 (UTC)

That shouldn't be related, this task was only about hiding a link from the sidebar. I don't know which Link 4inHand exactly clicked on, but the remaining download as pdf link there should work just fine. hgzh 16:08, 22 July 2024 (UTC)

@Hgzh Thanks for your reply. Anyway, I filed a ticket phab:T370740. SCP-2000 (talk) 04:30, 23 July 2024 (UTC)

Use of (also ...) at the beginning of an article

Hello - I am a newer editor and have potentially placebo'd myself into thinking there is a feature, where there is only a delayed update.

By using the phrase (also ...) at the beginning of an article on Wikipedia, does this automatically remove that parenthetical in the page preview? If so, is this behavior documented anywhere FAQ-y (are there other ways to do it)? Tule-hog (talk) 07:31, 22 July 2024 (UTC)

@Tule-hog: Hello, could you please elaborate benefits of the feature (why should this be implemented?) and provide some examples? Thanks. SCP-2000 (talk) 15:22, 22 July 2024 (UTC)

For instance when previewing Wikipedia:Computer security (on Wikipedia ofc so the preview actually shows up), the section which says "(also cybersecurity, digital security, or information technology (IT) security)" i.e. simply a list of alternate names, can be skipped over in favor of the actual summary of the article.

To clarify, this isn't a feature request (although I suppose it could be. As a request I might alter the idea to be a dedicated markup tag like `<skip>`, or a wiki template, instead of keywords or symbols to avoid breaking anything unintentionally). I finally managed to find another article that verifies what I am looking for: Wikipedia: Computer forensics. The portion "(also known as computer forensic science)" does not appear in previews, but has been that way for a while. I am wondering if there is explicit documentation about this feature. Tule-hog (talk) 00:17, 23 July 2024 (UTC)

Suggestion: Interwiki Page previews

This feature would only really benefit editors/admins, given that we generally should not be using interwiki links in mainspace articles. That said, I've found myself hovering over interwiki links a fair amount to get a quick glimpse at a photo or header line. (One common case for me is comparing simple.wiki with en.wiki articles.) An additional indication of which site is being displayed could prevent confusion. Tule-hog (talk) 18:16, 18 August 2024 (UTC)

Récent Changes in Wikipedia

Sorry for my poor english. I am french. Recent changes in Wikipedia result in very inconvenient problems :

I do not have the four tabs or thumbnail I use to have in my list (pages, others, all, etc…) which result in one tab only very often saturated with only the last change and my own changes never appear anymore. Simultaneously, I cannot thank someone anymore when seeing its changes and the corresponding diff. i am using an iPhone and would be grateful to correspond by voice

regards Sadlerhm (talk) 12:31, 2 September 2024 (UTC)

en:Template:Current election unreadable iOS

The template should display the following warning

This article documents a current election. Information may change rapidly as the election progresses until official results have been published. Initial news reports may be unreliable, and the last updates to this article may not reflect the most current information. Please feel free to improve this article or discuss changes on the talk page. (November 2024)".

Instead, it displays anywhere from the first few words to the first sentence and a half, depending on font size. Documentation leads me to believe that this is a case of local formatting being overridden. Can anything be done to fix this? McYeee (talk) 00:34, 5 November 2024 (UTC) also available at en:User:McYeee

Good news: This bug does not happen in article space. It's still an issue in talk space. McYeee (talk) 01:05, 5 November 2024 (UTC)

The issue applies to any sufficiently long text put in an en:Template:Ambox. McYeee (talk) 07:30, 7 November 2024 (UTC)

Dark mode Page Preview of black/white diagrams

It's long been an annoyance to me that the Page Preview functionality doesn't show dark images with light/transparent backgrounds with the inversion filter assigned with class=skin-invert-image. It makes previews for molecules like en:Ethanol, en:Glucose or en:Tartaric acid unreadable. I can't determine if this is a bug/known issue, something that is waiting to be implemented or an issue on my side. Is there a remedy for this? Synpath (talk) 22:35, 21 November 2024 (UTC)

Page previews last too long

I like the page previews idea, but they became very annoying because they stay open way too long -- I never timed it, but it was at least 15 seconds sometimes. Instead of disappearing when I move the cursor, they just block what I'm trying to read. So I turned it off. But I found I missed it, so I found out how to turn it back on (it wasn't easy -- had to search quite a while). And when I had it functioning again, I saw that it had reverted to the way it used to be -- vanishing when you moved the cursor. So I don't know what was going on, but it's like disabling and reenabling kind of cleared a cache or something. ??? Wlegro (talk) 07:14, 30 January 2025 (UTC)

Actually, no -- disabling and re-enabling didn't help for long. One page I'm reading -- or trying to read -- has had a page preview blocking the text for a couple of minutes now. The page is The Murder of Pop Smoke, and the preview is of a celebrity woman who owned the house he was murdered in. It's been there for the whole time it's taken to write this comment, plus the time it took to search my history looking for this page, including all the pages that weren't the right page, plus the time it took to read what I wanted about that celebrity. The only way to get rid of it is to hover over another link that opens another preview. That new preview disappeared as soon as I moved the cursor off, and the original preview now also disappears when I move the cursor off. Clearly there's some glitch going on, and I may just have to turn off Page Preview again, as cool and informative as it is.

Also -- I'm logged in but my user name is in red. ??? Wlegro (talk) 19:13, 2 February 2025 (UTC)

Project Pages

Within project pages of a wiki (like Wikipedia:), page previews don't work. Is there an explanation as to why? Justjourney (talk) 03:47, 11 February 2025 (UTC)

You want to read about $wgPageImagesNamespaces in Extension:PageImages. Tactica (talk) 02:23, 10 June 2025 (UTC)

Page Previews on Monobook

Only when using the Monobook skin, recently (a few months?) the font size of page preview popups became very small for unknown reason. Try https://en.wikipedia.org/w/index.php?title=anything&useskin=monobook Bultro (talk) 16:52, 22 February 2025 (UTC)

Page previews bug showing wrong image when display stub biography with no image.

1. Search "Hidayatullah dari Ternate" in idwiki https://id.wikipedia.org/w/index.php?search=Hidayatullah+dari+Ternate&title=Istimewa%3APencarian&profile=advanced&fulltext=1&ns0=1&ns1=1&ns2=1&ns3=1&ns4=1&ns5=1&ns10=1&ns11=1&ns14=1&ns15=1
2. Found the result on the right

   

3. Images displayed in result #1 and #3 clearly wrong. Found out because the image was used in the stub template: https://id.wikipedia.org/w/index.php?title=Templat:Indo-bio-stub

Image preview should not take the image from the stub template and assume it's the image of the article. Bennylin (talk) 06:22, 16 March 2025 (UTC)

Unless I'm missing something that's to be expected because the image scores big enough to be considered (size, aspect ratio, etc.) and the content of the stub template isn't explicitly excluded. See Extension:PageImages#Can_I_exclude_certain_page_images?. Tactica (talk) 02:19, 10 June 2025 (UTC)

Page previews for phab code issues

For some reason I was redirected here from Talk:Page Previews so I'll ask here.

Could you add page previews for phab issues like phab:T24660? Currently it's just an ID with no way to see what the issue is about. It would just show the issue title. Maybe it could also show some of the text or the number of subscribers but the thing that's important is that it displays the issue title. This would also be useful for the Community Wishlist where phab issues are often linked in wishes. Maybe it's not very difficult to fetch the issue title and display it in the page preview for the phab link. Prototyperspective (talk) 18:09, 18 March 2025 (UTC)

Phabricator workboards

It looks like a few Phabricator workboards for Web Team-stewarded components currently have custom filters as their default views:

• The MinervaNeue workboard's default filter hides all tasks that were filed more than two years ago, in addition to tasks marked as 'In progress' or 'Stalled';
• The Vector 2022 workboard's default filter hides tasks that are marked as 'In progress', in addition to tasks tagged with some projects;
• The Core-Skin-Architecture workboard's default filter hides tasks that are marked as 'In progress' or 'Stalled';
• The MobileFrontend workboard's default filter hides all tasks that were filed more than two years ago, in addition to tasks marked as 'In progress' or 'Stalled', tasks tagged with some projects, and tasks with the 'Unbreak Now!' priority.

Does the Web Team have any objection if the default view on these workboards is changed to all open tasks being shown on the workboard? The reason I ask is because IMO, when viewing a codebase’s workboard, a person would generally expect to be shown all the open tasks for that codebase, unless they personally choose to apply a more restrictive filter. (If the current filters are helpful, one idea I had is that a link to apply the filters could potentially be added to the sidebars of the respective workboards.)

cc @Jdlrobson. Best, ‍—‍a smart kitten_[meow] 09:18, 9 April 2025 (UTC)

Pinging @SGrabarczuk (WMF) in case this hasn’t been seen yet by anyone in the Web Team — I’m not sure who the best people from the Web Team would be to ping about this, are you aware of who might be best to ask? Apologies if you’re the wrong person to ping here! Best, ‍—‍a smart kitten_[meow] 09:53, 15 April 2025 (UTC)

It's alright, I have let the team know. I'm guessing that it's useful to hide the tickets Web won't be working on soon, and which we are working on now. This seems to be the classic discrepancy in needs where Phab is both a public repository (which is supposed to be providing the full information), and a working space for the team members (which should be useful and not distracting). SGrabarczuk (WMF) (talk) 10:27, 17 April 2025 (UTC)

Thanks for letting them know :)

With regards to the dilemma you mention, I wonder if anyone at Talk:Phabricator/Help might have any ideas about how to address it? I can see where you're coming from on this, and I'm not immediately sure myself on what the best way to resolve it might be. (The idea I had earlier was to add a link to the sidebar to apply the filter, but other people might have better ideas than that!) Best, ‍—‍a smart kitten_[meow] 11:26, 17 April 2025 (UTC)

The workboards tend to be aimed at the maintainers using the codebase (and guiding potential contributors on what would be useful to contribute towards that is likely to get reviewed/merged).

If you want to see all open bugs it is better to do use the search functionality

You can also request a User boards (e.g. https://phabricator.wikimedia.org/project/view/2985/) to triage particular bugs you are interested in.

Hope this is helpful Jon (WMF) (talk) 23:58, 9 May 2025 (UTC)

Thanks for the info, Jon (WMF)! To be honest, the main thing that prompted me to leave this message/look into this in the first place was the fact that the #MinervaNeue workboard hides all tasks that are more than two years old. To remark on this part of the filtering in particular, it struck me that this seemed like a way of making long-lasting bugs (which might include pain-points that many people would be happy to see resolved) less likely to get fixed, as it reduces the number of potentially-willing developers that might come across those particular tasks at all.
(As a case in point — I remember that I only came across phab:T381820 as I happened at one point to be looking across the MobileFrontend (MobileFrontend Special Pages) workboard. If that workboard filtered out tasks by age, and if that task had been older than the workboard's selected age limit, I wouldn't have come across it & therefore wouldn't've been able to submit a patch that resolved it.)

Regarding user boards in particular -- I've thought about the idea of requesting one before; but a user board wouldn't be helpful to me in this particular scenario, as I was more making a comment about how the workboards display tasks to people in general (rather than thinking that I might be interested in triaging any particular tasks on those workboards myself).

I wonder if it's worth a wider discussion (maybe at Talk:Phabricator/Help?) about the general idea of workboard filtering for Phab projects that represent a software component (as opposed to e.g. team projects)? While I recognize a need for developers (including/especially code stewards) to be able to filter tasks sometimes in order to be able to work effectively, it does IMO feel potentially confusing to limit the open tasks that appear on a software component's workboard based on (what are IMO) fairly blunt heuristics. I'm gonna ping AKlapper (WMF) in case he has any insights here, as someone much more experienced with Phabricator/bug-tracking than me! Best, ‍—‍a smart kitten_[meow] 15:16, 11 May 2025 (UTC)

It is up to stewards/maintainers/developers/team of a software component which workboard items to show or hide. Whatever supports them best in their work. :) If folks want to see full or different filtered results, folks can temporarily change the filter. AKlapper (WMF) (talk) 17:04, 11 May 2025 (UTC)

phab:tag/Advanced Mobile Contributions

@Jon (WMF), just noting that I edited the (now-archived) project’s description to include a pointer towards other projects for future AMC-related tasks to be filed under. Obviously please feel free to modify as desired - I'm letting you know in case I got any of it wrong/in case there are better Phabricator tags to point people towards :) Best, ‍—‍a smart kitten_[meow] 18:00, 24 April 2025 (UTC)

Thanks that's great! The project is somewhat redundant now, as it was aimed at special pages in MobileFrontend and most are no longer overriden by the MobileFrontend codebase. Jon (WMF) (talk) 23:52, 9 May 2025 (UTC)

TOC invisible on mobile

Hi! The table of contents of a Wikipedia article is invisible on a mobile phone with a screen width of less than 640px. Why is that? The result is that only the top-level paragraph titles are visible (and their content visible through clicking on this title). No subtitles are clickable. No other way of viewing the complete TOC of an article is available.

This is counter-intuitive for article development, as it seems to benefit a culture of making article dispositions without subtitles and/or a flatter hiearchy. It also presses for shorter articles, as viewers otherwise will have to scroll more to reach for content (clickable subtitles lacking). I hope there is a way of letting a complete – and clickable – TOC be visible also on mobile phones per standard. Paracel63 (talk) 11:20, 5 May 2025 (UTC)

It just hasn't been built yet. Jon (WMF) (talk) 23:51, 9 May 2025 (UTC)

The associated task is https://phabricator.wikimedia.org/T147026 and the eventual hope would be to port something similar to the Vector 2022 skin experience to Minerva Jon (WMF) (talk) 23:52, 9 May 2025 (UTC)

Reading/Web/Projects/Mobile Page Issues/22

Is the translation unit labeled correctly? ENeRZet (talk) 09:41, 9 May 2025 (UTC)