Talk:Reading/Web/Desktop Improvements

Overview

Features

Repository

FAQ

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. (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)

How to disable Vector 2010 legacy, and keep only Vector 2022 in settings ?

... Mystrixo (talk) 13:36, 27 March 2024 (UTC)

@Mystrixo: Hello, you can follow this instruction to enable Vector 2022 on either one or all wikis. SCP-2000 (talk) 06:39, 28 March 2024 (UTC)

Hello @SCP-2000, Thank you very much I really appreciate your help!,

but I am referring to a mediawiki settings to disable Vector 2010 for users (on my personal wiki) Mystrixo (talk) 08:05, 28 March 2024 (UTC)

Can you help us understand why you want to do this? There may be an easier/better way, depending upon the reason. Safety Cap (talk) 15:42, 15 April 2024 (UTC)

@Safety Cap We are moving toward a more responsive mediawiki skin, I guess. Although I am yet unable to observe any responsiveness in Vector 2022, I assume that this is planned and that I should discard the old skin because it is not mobile-friendly. Thank you for your inquiry. Mystrixo (talk) 01:49, 20 April 2024 (UTC)

Ahh, makes sense. Interestingly, Wikipedia appears to use Minevera when in "mobile mode" (https://en.m.wikipedia.org). I ran some tests and both Vector 2020 and 2022 are not responsive, as you indicated. Safety Cap (talk) 19:55, 21 April 2024 (UTC)

The Vector 2022 is not designed for the mobile device. You can use Minevera for the mobile device, or using other skin like Timeless / Citizen. Thanks. SCP-2000 (talk) 16:38, 23 April 2024 (UTC)

In my opinion, MediaWiki need to create a single, uniform skin that combines the classic UI of the Vector2010 skin with a contemporary, mobile-friendly UI to provide a uniform user experience. This would eliminate the need for many confusing skins. Mystrixo (talk) 11:31, 24 April 2024 (UTC)

You may be interested in https://phabricator.wikimedia.org/T106463 to track improvements to Vector 2022 on mobile.

Note you can use Manual:$wgSkipSkins to disable Vector as a skin. Jdlrobson (talk) 03:11, 2 May 2024 (UTC)

cant go to 2010 legacy

everytime i try to change from the vector 2022 to the vector 2010 it dosen't work, it says its change but its just locked into the 2022 version, anyone else having this problem and have a fix? Purpetic (talk) 00:21, 3 June 2024 (UTC)

Hello @Purpetic, thanks for coming here to ask this question. What option do you use to change the skins? Is it the link in the sidebar, or do you go directly to preferences? SGrabarczuk (WMF) (talk) 14:41, 4 June 2024 (UTC)

To update to the 2010 legacy, go to Settings -> Preferences -> Aspect. Select your preferred version (i.e. Vector legacy (2010)) and click on the save button. Refresh the page or clear your browser data to apply the changes. 49.236.20.80 18:08, 4 June 2024 (UTC)

CSS issue

Tracked in Phabricator
Task T366314

The right sidebar goes underneath the main content in small screens

Hello! I'm an interface admin from SqWiki. Can someone help me fix an issue on it with the 2020 Vector skin? The screenshot shows what I currently get in there if the window is not large enough. The tools sidebar on the right side goes underneath our page, instead of pushing it to change the layout (like the toolbar on the left does). This should be related to our layout but still don't understand properly why the right sidebar behaves differently from the left one and how to target and modify it so they behave the same. - Klein Muçi (talk) 08:13, 5 June 2024 (UTC)

Hello @Klein Muçi, thanks for coming here. I believe T366314 should solve the problem. We'll be rolling it out in the coming weeks - it's difficult to tell when exactly because there may be blocking bugs. SGrabarczuk (WMF) (talk) 15:03, 6 June 2024 (UTC)

SGrabarczuk, oh, okay then. No problem. Thank you for letting me know it's being worked on. — Klein Muçi (talk) 09:31, 7 June 2024 (UTC)

I'm back sooner than I was expecting to. Now our headers have gone completely out of proportions in Vector legacy. Can you point me on any way on how to address that? - Klein Muçi (talk) 07:18, 9 June 2024 (UTC)

Was able to handle it with the instructions explained here: Heading HTML changes — Klein Muçi (talk) 23:54, 10 June 2024 (UTC)

Common.css and Vector.css are loaded too early

Hi. I am trying to make some modifications in the CSS for the entire site (a small private wiki), more specifically setting a washed out backdrop picture for the site. It should be easy with CSS from Common.css or Vector.css but it appears that both are loaded quite early and overwritten by the skin's own CSS (I presume @media screen... comes from the skin).

I would expect Common.css and Vector.css to be loaded last, so we have a chance of modifying the "final" CSS before displaying. Steff-X (talk) 13:10, 6 June 2024 (UTC)

What version of MediaWiki are you using? Jdlrobson (talk) 14:03, 6 June 2024 (UTC)

How to sharpen the font

After 2022, when it was imposed on us, I'm again back to Vector 2022 temporarily. There has been a regression with XfDCloser on enwiki with Vector 2010, so I have to be on Vector 2022 until that is fixed (See https://en.wikipedia.org/wiki/Wikipedia_talk:XFDcloser#XFDCloser_not_showing_up_in_Vector_2010 )

How do we make the fonts same as Vector 2010. In 2010 the fonts are sharp and easier to read. In Vector 2022, the fonts are faded/jaded/less black/blurred and makes it harder to read. Any customizations we can do? Jay (talk) 09:13, 8 June 2024 (UTC)

TOC updates?

I'm back on Vector 2022 after an year and a half, and notice no improvement on the TOC. At /Archive7#TOC level we had discussed about maintaining the top level TOC only, but I still see the full expansion of multiple levels at en:Wikipedia:Redirects for discussion#Current list making it unusable. At that discussion User:Shells-shells had tried explaining the issue to User:OVasileva (WMF).

At /Archive8#Old style TOC in Vector-2022 Skin, User:Jonesey95 had provided a FAQ entry (which I had tried without success), but now that entry is missing in the FAQ. User:SGrabarczuk (WMF) had said he would ask the developers in the team to update the script that will bring back the old TOC, but I see that was the last post of that discussion.

Also, since we are at TOC, is there a way to make the TOC (of talk pages) concise? I do not wish each entry to be on two lines, where the second line mentions the number of comments. Looking for a simple one line per entry kind of TOC. Jay (talk) 20:38, 12 June 2024 (UTC)

Hey @Jay, thanks for the reminder! The reason why not much in the TOC has changed over the last 1.5 years is that since last year, we've been focused on a new project - Accessibility for reading. Before that, we did have some feedback about TOC, but I guess the direction wasn't clear enough for us to make more changes. Currently, we're revisiting tasks related to Desktop Improvements, and we'll definitely talk about the issues you're pointing at.

Regarding the TOC of the talk pages, that's actually part of the Talk pages project by a different team. The goal for introducing this second line was for junior contributors to be able to tell more easily that what they're seeing is a TOC of different discussions, and not a TOC of article sections. Because adding that second line was on purpose, I guess that the only way to disable it is by adding .ext-discussiontools-init-sidebar-meta {display:none} in your personal CSS.

I wholeheartedly encourage you to subscribe to our newsletter. We send messages whenever there's important news to share. You won't miss anything if you subscribe. Thanks! SGrabarczuk (WMF) (talk) 22:54, 12 June 2024 (UTC)

As with the Visual Editor, which was in beta for something like ten years, the WMF developers have for the most part moved on from development of Vector 2022. Straightforward fixes like making the sticky header consistent with the default top-of-page header (no progress since June 2023), or making the sticky header visible on all pages (no progress since February 2023), are stalled. See the task board for more status information. I recommend that you explore the various CSS adjustments that you can apply to your personal vector-2022.css file. See en:User:Jonesey95/common.css for the fixes that I have applied to make Vector 2022 usable on my computer. Jonesey95 (talk) 04:13, 13 June 2024 (UTC)

Somewhat unrelated: I believe that the number of comments shown below each talk page heading in the TOC is provided by the Beta feature called "Discussion Tools". You can disable that Beta feature in your Preferences. I could be wrong about this. Jonesey95 (talk) 04:16, 13 June 2024 (UTC)