Talk:Reading/Web/Desktop Improvements
![](http://upload.wikimedia.org/wikipedia/commons/thumb/b/bb/Welcome_in_21_languages.svg/220px-Welcome_in_21_languages.svg.png)
You can comment in any language. We are especially interested in:
- Feedback on the functionalities we have already deployed. (Please see Reading/Web/Accessibility for reading/Known issues before reporting bugs.)
- 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)
![]() The following Wikimedia Foundation staff monitor this page: ![]() ![]() OVasileva (WMF) Timezone: UTC+1/2 Language(s): en, es, bg
|
---|
![]() Archives
|
---|
Archive1 · Archive2 · Archive3 · Archive4 · Archive5 · Archive6 · Archive7 · Archive8 · Archive9 · Archive10 · Current discussion |
retest content separation wen
[edit]@SGrabarczuk (WMF) In the last update, you mention As we reported previously, the A/B test didn't prove that the color-based separation was an improvement.. However, that's not what the previous update really concludes. The previous update concluded that the prototype was flawed for small screen sizes and recommended Introducing improvements to Zebra, optimizing for narrower screens, and repeating the tests.. Aaron Liu (talk) 14:03, 2 July 2024 (UTC)
- Hey @Aaron Liu - thanks for the question! So we tested this idea in two contexts. The first was the prototype testing in a user testing context (testing with a small group of readers who give us feedback). The results of this test are available on this page. Here we found that, while there wasn't a noticeable different in readability that we could measure between the two versions, users did say they have a slight personal preference towards the newer version. Based on this, we decided to proceed testing this version on a larger scale. The second test, which was the A/B test on the feature is the one that showed us issues that showed us that, were we to proceed with this, we would need to go back to the drawing board. While this is still a possibility for the future, we haven't prioritized it yet as, based on the user testing, we don't have a strong proof that it would be significantly helpful to readers and editors. OVasileva (WMF) (talk) 09:04, 23 July 2024 (UTC)
- Hey @OVasileva (WMF), the A/B test on the feature seems to be the same one reported in the previous update. See my last sentence. Aaron Liu (talk) 14:38, 23 July 2024 (UTC)
Bumping this to avoid archiving before resolution. Aaron Liu (talk) 11:51, 5 September 2024 (UTC)
CSS issue with category infoboxes
[edit]![](http://upload.wikimedia.org/wikipedia/commons/thumb/0/0b/Vector_CSS_issue.png/220px-Vector_CSS_issue.png)
Using the Vector skin in dark mode makes the title link in category infoboxes completely invisible. The infobox in the screenshot has the title "Organised labour" but the color of this title is black against a black background Other links are perfectly readable. Etothepi16 (talk) 16:18, 6 July 2024 (UTC)
- @Etothepi16: Thanks for flagging this. I have reported this issue on the Reading/Web/Accessibility_for_reading/Reporting/en.wikipedia.org#Labour_movement_dark_mode_error. SCP-2000 (talk) 04:38, 1 August 2024 (UTC)
Expand table of contents
[edit]Is there a way for the table of contents to always be expanded? Some articles have the table of contents expanded but others don't. Thanks. Along517 (talk) 00:24, 18 July 2024 (UTC)
- @Along517: Hello, generally your preference would be remembered, and thus the table of contents should always be either expanded or collapsed. Which pages have this issue? Thanks. SCP-2000 (talk) 04:21, 1 August 2024 (UTC)
- Hi, thanks for responding. Sorry if this is the wrong place but I meant for the normal Wikipedia. This happens whether I'm logged in or not. An example is if I go to Lionel Messi's page, all the contents on the left are expanded while Cristiano Ronaldo's table of contents is not expanded. Along517 (talk) 21:52, 3 August 2024 (UTC)
- @Along517: Hello, thanks for the information. Did you see the ToC like this screenshot https://ibb.co/frqJkDP or this one https://ibb.co/VmJYCKd? If it's the second one, it may be due to the narrow screen. If it's the first one, have you tried using another browser or device to visit that page? SCP-2000 (talk) 04:43, 4 August 2024 (UTC)
- It looks like the first one more. (https://ibb.co/nzYSTF6). Here's what it looks like not expanded (https://ibb.co/CPXcxwR). I've tried other browsers (Firefox and Safari) and it has the same results. Along517 (talk) 16:22, 4 August 2024 (UTC)
- @Along517: Thanks for your reply. I apologize for my misunderstanding, and I thought you meant the entire part of the ToC was not expanded. Nevertheless, it seems that sections are not expanded by default if there are 28 (or another value) or more sections regardless of level. You may use the userscript listed in this post on Special:MyPage/vector-2022.js to expand all section on ToC. SCP-2000 (talk) 16:26, 5 August 2024 (UTC)
- Thanks for the tip! Along517 (talk) 01:37, 6 August 2024 (UTC)
- @Along517: Thanks for your reply. I apologize for my misunderstanding, and I thought you meant the entire part of the ToC was not expanded. Nevertheless, it seems that sections are not expanded by default if there are 28 (or another value) or more sections regardless of level. You may use the userscript listed in this post on Special:MyPage/vector-2022.js to expand all section on ToC. SCP-2000 (talk) 16:26, 5 August 2024 (UTC)
- It looks like the first one more. (https://ibb.co/nzYSTF6). Here's what it looks like not expanded (https://ibb.co/CPXcxwR). I've tried other browsers (Firefox and Safari) and it has the same results. Along517 (talk) 16:22, 4 August 2024 (UTC)
- @Along517: Hello, thanks for the information. Did you see the ToC like this screenshot https://ibb.co/frqJkDP or this one https://ibb.co/VmJYCKd? If it's the second one, it may be due to the narrow screen. If it's the first one, have you tried using another browser or device to visit that page? SCP-2000 (talk) 04:43, 4 August 2024 (UTC)
- Hi, thanks for responding. Sorry if this is the wrong place but I meant for the normal Wikipedia. This happens whether I'm logged in or not. An example is if I go to Lionel Messi's page, all the contents on the left are expanded while Cristiano Ronaldo's table of contents is not expanded. Along517 (talk) 21:52, 3 August 2024 (UTC)
Zur Seite in anderer Sprache verlinken | Link to a site in another language
[edit]In Vector 2010 ist es einfach möglich im unteren linken Bereich auf „Links hinzufügen“ zu gehen, dann kam so ein Popup-Fenster, man trug das Ziel ein und fertig. Falls es schon mindestens ein Eintrag gibt, steht da stattdessen „Links bearbeiten“ und man wird auf Wikidata weitergeleitet, was ja in Ordnung ist.
Bei Vector 2022 habe ich die erste Möglichkeit nicht. Entweder ein Fehler oder es ist woanders... Sven792 (talk) 22:23, 31 July 2024 (UTC)
- @Sven792: Hello, it is not the bug. Here is the previous discussion and the relevant phab ticket for your reference. Thanks. SCP-2000 (talk) 04:06, 1 August 2024 (UTC)
- Thank you. It is just somewhere else. You need to make a new Wikidata item yourself though, it seems? Sven792 (talk) 12:19, 1 August 2024 (UTC)
- @Sven792: Yes, if there is no Wikidata item, then you have to create a item on Wikidata manually or by the gadget (if any). SCP-2000 (talk) 16:54, 1 August 2024 (UTC)
- Thank you. It is just somewhere else. You need to make a new Wikidata item yourself though, it seems? Sven792 (talk) 12:19, 1 August 2024 (UTC)
You've made it harder to add interwiki links
[edit]As an unregistered user, I used to be able to easily link articles on two wikis. I could do this from the Wikipedia article itself, from the pencil icon on the sidebar, typing in the language code, typing in the article title, then done! Added to Wikidata, whether or not a Wikidata item previously existed! Now, there's a nice looking box that says "Add languages", but if I click it, there's no way to add a link to another Wikipedia page! The only way to do it is by going to Wikidata. You've decreased functionality here! Please fix this; it is very irritating. 2601:644:9083:5730:3875:489:C235:7014 23:16, 2 August 2024 (UTC)
Infobox section display error on mobile
[edit]![](http://upload.wikimedia.org/wikipedia/commons/thumb/3/32/Infobox_display_error.jpg/220px-Infobox_display_error.jpg)
This error appears on infoboxes on the mobile web version of Wikipedia, where double lines appears below section headings (such as Government, Formation, etc. as shown below) and single lines appear seperating every single line. This error appears on the mobile as well as the desktop layouts in the mobile version of Wikipedia (one where the links start with en.m.wiki [...]), but does not appear on the desktop web version (en.wikipe [...]). I'm not sure if this is the correct spot to report this error, and I'd be glad if someone could tell me what to do in this situation. PadFoot2008 (talk) 08:09, 27 August 2024 (UTC)
- This is an error in the template generating the infobox, where the infobox is emitting an empty row. That causes problems like this. P.S. Next time, please link to pages where you see a problem, so that we don't have to type over the content of a screenshot into a google search, in order to find the article. —TheDJ (Not WMF) (talk • contribs) 10:21, 4 September 2024 (UTC)
Inappropriate images shown in search results
[edit]When I look for w:Scroll on enwiki in vec2022 (i made the switch a few days ago), the infobox image for w:Scrotum shows in the tentative search results as I type. While I get that Wikipedia is not censored, I do find it a bit odd that we show inappropriate images to users who have expressed absolutely no interest in seeing them. Like, if I actually navigated to the latter page, that's on me, but users should have the ability to choose their UX and this is not that. Theleekycauldron (talk) 06:56, 6 September 2024 (UTC)