Talk:Reading/Web/Desktop Improvements

Where is the TOC?
People here are complaining about it. I don't even get one! Betaneptune (talk) 17:38, 25 May 2022 (UTC)


 * Hello @Betaneptune. Do you still have this problem? SGrabarczuk (WMF) (talk) 17:52, 8 June 2022 (UTC)
 * Hi ! I have the same problem on the French version of Wikipedia. The TOC just disappeared. The problem appears in Firefox desktop (last version 101.0.1), even in "troubleshoot" mode with all my add-ons deactivated. However, the problem does not appear in Chrome. This is extremely confusing. I reported it on some discussion page on the french version of WP, but I also mention it here, as I'm not sure at all where to report the problem for it to be taken into account. 85.169.195.108 17:56, 26 June 2022 (UTC)
 * The TOC is now on the left side, but after other menu lists. It should probably come first. But to keep things accessible, the (hidden) "jump to main menu" link should be kept as first element of course. Psychoslave (talk) 15:00, 5 July 2022 (UTC)
 * Agreed. The TOC really should come first. The #mw-navigation menu (which currently appears first) is comprised of mostly ancillary links unrelated to the page's content, many of which are rarely used (e.g., "Download as PDF", "Create a book", "Permanent link", etc). OmenBreeze (talk) 00:17, 6 July 2022 (UTC)
 * It has been tracked here T312022.--37.103.14.65 09:03, 7 July 2022 (UTC)
 * Suggestions:
 * If the TOC will not come first, the other menu lists on the left side should become hidden (collapsed) when there is a TOC below them, so that the TOC is always visible.
 * The TOC should always be shown in its entirety, and not displayed as a box that you have to scroll through.
 * Förbätterlig (talk) 14:03, 12 July 2022 (UTC)

Too narrow (again)
Why waste all that space? I have a nice wide screen so I want to take advantage of it. Those who want to have it narrow can just reduce their window sizes? Overall, not a great look. Not exciting. Quite boring.--Xania (talk) 11:23, 22 December 2021 (UTC)


 * Hello @Xania, you can read about our goals and motivation for limiting the width. Also, we are working on a solution to use the empty space. Could you take a look at our fourth prototype and write more on what you think about arranging the space as it is presented there? Thank you in advance! SGrabarczuk (WMF) (talk) 14:59, 26 April 2022 (UTC)
 * Oh my dear God, why don't you give an option to unrestrict the width?? It's beyond ridiculous how absolutely tiny is the page content on my monitor horizontally! I have to scroll all the time to read! Don't ruin Wikipedia the same way Fandom was ruined! 90.188.46.13 04:38, 13 May 2022 (UTC)
 * We have given this option. This can be done with the gadget one of our engineers made. SGrabarczuk (WMF) (talk) 03:39, 14 May 2022 (UTC)
 * Thanks, but maybe we should have an easy plug-in system for ordinary users or, at least, the instructions how to apply it and a place where to find those customisations. By default it is really narrow to read and it feels like a news site rather than an encyclopedia article. Krnl0138 (talk) 09:55, 15 May 2022 (UTC)
 * I agree, the toggle option should be there by default! By the way, that script does not work well currently, so I updated it here. — Arthurfragoso (talk) 13:28, 21 May 2022 (UTC)
 * I don't understand why you are still pushing on us that bad design choice. It still is time to pull the plug and start to work on a plain page design. You are convincing no one here. Please, please, really, please stop this nonsense. Forcing bad choices on your users because you are the only product on the market is never a good thing.
 * Since it has been forced without asking anyone on the French Wikipedia I had to register just to come back to the normal and good design. That's something, as a simple reader, I should never have had to do in the first place.
 * So one last time, please come back to reason and stop hurting your user base foolishly. DerpFox (talk) 21:33, 13 May 2022 (UTC)
 * Hello @DerpFox, thanks for your comment. Have you maybe followed the links I've shared in my answer to Xania? SGrabarczuk (WMF) (talk) 03:42, 14 May 2022 (UTC)
 * The lines in the fourth prototype seem to be slightly wider to me on 1080p display than in the current version of 2022 vector design, but those empty strips on the sides, each of which are almost the size of the old navigation mv-panel, constantly remind about the space wasted.
 * If the only reason of this thinning is the recommended line lengths in symbols and you want to keep it for any price, I would suggest using a dynamic font size, so, for example, starting from some resolution the symbols just grow larger. This might also reduce the eye strain connected to focusing on the small text.
 * Kageneko (talk) 13:51, 17 May 2022 (UTC)
 * I had a browse over the reasons for the change, but I still don't like or agree with the main justification more or less boiling down to "everyone else is doing it so we should too". Even in the linked examples, the page still feels a lot more "full" despite having a dedicated deadspace on the site, due to the way the page has been very carefully designed in a mixture of different kinds of block contents (images, text interactive eliments, etc).
 * Accepted Webpage standards used to be against having blank, unused and waisted deadspace, but at some point in the last 10 years there seems to have been a weird shift to the opposite where deadspace is all the rage, though it's not one I've personally ever liked or agreed with.
 * While I'm sure there are good uses of limiting page width, I'm not sure if Wikipedia, being a site that is mainly made up of text would really benefit from it as it's likely just going to squash pages and increase the amount of vertical scrolling required to navigate. Dave247 (talk) 07:32, 18 May 2022 (UTC)
 * Yeah it's too narrow otherwise. the look is very nice, it's not boring as you tell. Crater bug (talk) 15:28, 28 May 2022 (UTC)
 * I totally agree! I dislike the vector skin because how small it is. OverAWallOfMetaKnight (talk) 15:55, 15 May 2022 (UTC)
 * Agreed. I use a 3440x1440 screen (usually with a tiled layout), and this new layout forces all the content to occupy a comically narrow strip, instead of allowing me to choose the width myself. Emptyflask (talk) 13:47, 17 May 2022 (UTC)
 * I agree, there is simply too much space wasted that could be used for more article space and a button specifically for those who want to edit wikipedia Techny3000 (talk) 02:52, 28 May 2022 (UTC)
 * hard to read I'm glad I stayed the same as before No changes required 240B:11:E7E0:5E00:6005:3399:E6C:2B48 14:06, 2 July 2022 (UTC)
 * Strongly agree. I want to decide the readable width for me. In the old skin and most websites, I can do it by adjusting the width of window. I definitely don't want to care about "CORRECT READABLE WIDTH FOR EVERYONE" decided by someone somewhere, even if they are great scholars. Kyoku (talk) 08:32, 10 July 2022 (UTC)
 * Agreed wholeheartedly. By the way, the design is even worse on a low DPI widescreen display, like 1366x768, 1280x800/720, etc. Try it out with Device Rendering options in your browser, usually somewhere in Dev Tools. I just got hit with Vector 2022 after coming here from wikipedia where I've had Vector 2010 enabled for a while and I forgot how bad it was!
 * Wikimedia Foundation, do not forget that people all around the world use your service. People who might have a budget/old device with a low resolution display, or schoolchildren with a Chromebook or something! No default layout should ever create this much dead space and padding in a desktop environment. NONE. Nor should it ever consume nearly 1/3 of screen real estate that can never ever be used by the main content.
 * The floating ToC looks like absolute garbage at 720p. I have WUXGA and 4K devices and it isn't any better there either. I'm not sure who the design is aimed at, other than the designers pushing the modern scourge of padding and white space onto the rest of the Internet. -αβοοδ (talk) 17:41, 29 July 2022 (UTC)

After reviewing the posted defense of the narrowing and the feedback listed here, this feature belongs entirely as an optional setting. It most certainly should not be the website's default. RightQuark (talk) 01:29, 24 May 2022 (UTC)
 * The defence of the narrowing seems to have little real-world bonuses. It may be theoretically good but makes it bad to read because Wikipedia articles can be long Torqueing (talk) 17:10, 24 May 2022 (UTC)

I also have a wide screen monitor. I do not like this forced width shrinkage in the Vector 2022 skin. OhanaUnited  Talk page  17:24, 9 June 2022 (UTC)

In current form without a toggle for width this layout is unacceptable on large monitors. Even my old 14'' monitor. For now I am reverting to avoid having in forced horizontal white-space. phatom87 (talk) 14:32, 20 June 2022 (UTC)


 * Absolutely unacceptable, too narrow, an unjustified waste of space. Loupeter (talk) 10:39, 24 June 2022 (UTC)


 * It sounds like the fixed-max-width (assuming one's window is wide enough, and regardless of how much wider it might be) is a compromise between the needs of two different types of reading activities. I have both habits (skim vs detail-read), and felt especially the concern that the text doesn't obey what *I* do with my window. A reason I might widen my window is exactly because I want wider content. A comprimse necessarily isn't ideal for either one side. A better solution is to make it easy and discoverable how to get the *best* feel for whatever one is trying to do, rather than forcing so many to have a sub-par experience. A third-party gadget isn't discoverable and is surely more fragile than a first-class toggle feature of the skin itself. DMacks (talk) 15:16, 29 June 2022 (UTC)

In my opinion, Skin:Timeless does a much better job at restricting article space to improve readability. This is because the UI is not entirely positioned on the left-hand side of the screen, and the background colour is not blindingly bright. If the intention is to create whitespace, please don't use bright colours. Timeless also has more space for pictures. For the past 20 years, articles have been written with the understanding that 80%+ of the screen will be for content. There are width and upright tags all over the place that, once viewed with this narrow a perspective, become overwhelming.

A skin should not change the fundamental readability of the page. Compare this with this. In Timeless, when the content ends, grey begins. In Vector 2022, it looks like the HTML was corrupted and failed to load because it continues with white for no discernable reason. Vector also artificially makes articles look longer than they are, which may actually dissuade people from reading. For instance, using a 27" 16:9 monitor, on the article for Barack Obama, Vector just about lets me see the entire lead on my screen at once. Timeless allows me to see the whole lead quite easily, as well as part of the ToC. Line length may be a thing, but you must take into account the total amount of text on the screen at once, too. There's no use having the perfect 50 character line if you need 100 of them all bunched up together. Anarchyte (talk) 13:18, 13 July 2022 (UTC)


 * Quick update and aside: I just learned about wide-vector-2022. This is fantastic. I actually like the ToC being placed where it is when using that gadget. If the plan was to make the wide skin the default, I would be less hesitant. For comparison with the links in my previous message, here is Barack Obama with wide-vector-2022. Anarchyte (talk) 13:25, 13 July 2022 (UTC)
 * This "wide-vector-2022" version should be the default IMO. Some1 (talk) 02:50, 17 July 2022 (UTC)
 * It's definitely an improvement, but Vector 2010 is still better. I agree with @Anarchyte - Timeless does a better job of restricting article space than Vector 2022 does. When you look at how much of the left third of the screen is blocked off from article content, Vector 2010 restricts it the least, followed by Timeless, and then finally by Vector 2022 consuming nearly an entire 1/3 of the screen. At low DPI, it's hilariously ugly, and arguably makes readability worse, not better. Vector 2022 sure would be nice though, if the ToC was collapsible! -αβοοδ (talk) 17:48, 29 July 2022 (UTC)
 * > For the past 20 years, articles have been written with the understanding that 80%+ of the screen will be for content.
 * I'll just note that for the past 10 years that means you've written things that just do not work that way on mobile. :)
 * > A skin should not change the fundamental readability of the page. [..] In Vector 2022, it looks like the HTML was corrupted and failed to load because it continues with white for no discernable reason.
 * This seems like a lot of assumptions to me personally. Do we have wider evidence for this ?
 * > There's no use having the perfect 50 character line if you need 100 of them all bunched up together.
 * Literally every mobile user on the Barack Obama page, the majority of the readers. Screens and screens till you hit the end of the lead... —Th e DJ (Not WMF) (talk • contribs) 20:20, 14 July 2022 (UTC)
 * I'll just note that for the past 10 years that means you've written things that just do not work that way on mobile. :)
 * MinervaNeue, when viewed on normal phone screens, ignores width tags. The only difference between writing for desktop screens and mobile screens is file placement.
 * This seems like a lot of assumptions to me personally. Do we have wider evidence for this ?
 * I don't need to provide evidence to state my opinion. The page looks unfinished with the extra whitespace on the right hand side. If you do want more than just my opinion, CNTRL+F for "whitespace" on this page. 12 other posts mention it.
 * Literally every mobile user on the Barack Obama page, the majority of the readers. Screens and screens till you hit the end of the lead...
 * Difference is that my phone is in my hand. I'm not getting overloaded with line after line if the screen is only 15cm long. I can see a whole paragraph on at once and then scroll when necessary. Anarchyte (talk) 13:10, 15 July 2022 (UTC)

Full-width sticky header
I'm fine with the text being narrow but the ui and nav bar should be full width. --Thedonquixotic (talk) 00:18, 26 May 2022 (UTC)


 * @Thedonquixotic, what do you mean by the ui and nav bar? SGrabarczuk (WMF) (talk) 17:54, 8 June 2022 (UTC)
 * Not sure what is unclear here. I mean the navbar. As in the bar up at the top of the page with use account, search etc. Thedonquixotic (talk) 19:07, 1 July 2022 (UTC)
 * OK, thanks for clarification, @Thedonquixotic. Let's take a look at this image. This will help us make sure what we're talking about. Now, the navbar (aka the header) is aligned to the workspace container, so is wider than the content container, but not as wide as the page container. The same applies to the sticky header. So you believe the header should be as wide as the page container? SGrabarczuk (WMF) (talk) 22:54, 4 August 2022 (UTC)

Consistent skin across the wikis
New Skin is burdening me when I switching between languages. (and I zoom when I want improve readability rather put blank space) it Should changing all language together if it is well received and appreciated. should not just some language for set a precedent. Mutyoro (talk) 19:27, 4 August 2022 (UTC)
 * @Mutyoro, thank you for your comment. First, if you want to have the same skin across all wikis, you can choose one global preferences. Secondly, the way how Vector 2022 becomes the default across more and more wikis - that's a complicated issue. Week after week, we roll out small changes to Vector 2022 that are visible across all wikis. At the same time, it's much easier (both for our team and for the communities) when some communities use this skin as the default earlier, and some get it later. SGrabarczuk (WMF) (talk) 22:54, 4 August 2022 (UTC)
 * Thanks for your comment, @SGrabarczuk (WMF),
 * Seems like I sent wrong message. what I want is, Change skin after agreed by each wikis.
 * Should not try to archive Bandwagon effect by using Sheeple.
 * Pease be aware "most of people like it because accept it" this is typical comment of crowd manupiration.
 * I thought 8 years ago some of your colleague try to narrowing width, and it was Rejected by users.
 * Talk:Typography refresh/Archive 2
 * do you have any information why try to narrower down even it was rejected before? Mutyoro (talk) 21:43, 8 August 2022 (UTC)

Feedback regarding the new language switcher
Hello, I am a French person using Wikipedia in both French and English. I usually decide the language of the article depending on the topic. If it's related to France, I know the French version is going to be better. If it's a general topic, I usually select English.

However, it's been a few months that the language picker has been moved to the top of the screen when an article is display in French. And I really can't get used to it. Sure, it's easy to discover - but it's more complicated to use. Having to click twice is a regression for anyone switching language frequently. An action that used to require half a second now takes 2 seconds. If you do this about ten times every time you browse Wikipedia, it does become irritating...

I hope this feature is not shipped to other languages, and France gets the sidebar back. If you want to make this feature more discoverable, maybe you could add a shortcut but keep the sidebar. Or display a tooltip once in a while to educate newcomers. But please, keep "heavy users" of language switching in consideration. Thanks
 * I'd state this as 'what used to take me a second (finding the right language) now takes 10': Open language switcher, often don't see the language I want, have to search?  want to see which languages have a version, have to scroll; don't have a quick way to default present all languages by-alpha. Sj (talk) 16:49, 2 May 2022 (UTC)
 * I have to agree with this as another French person frequently switching languages on Wikipedia and Wiktionary. I should add, in addition to the intrinsic usability of the interface (I do agree it's a slight regression for my usage), the fact that most language editions still use the old interface (and most other sites using mediawiki, and the latter is likely to remain the case for a long time) means you don't actually get the opportunity to unlearn it. So every time I want to switch languages from a French page, I will first scroll down to the old location and waste 1s parsing the sidebar and wondering where the links are. I check out other languages almost every time I read any article and those milliseconds of irritation do add up. Anyway, I strongly think that “don't fix what ain't broke” should apply here! 37.183.2.114 12:06, 8 May 2022 (UTC)


 * +1 to Sj. --ThurnerRupert (talk) 18:58, 11 June 2022 (UTC)

Often I use the language switcher not to navigate to the article on different language, but just to look up how that article is titled in a different language. In other words, using Wikipedia's inter-language links as a sort of dictionary. By hovering over the list of languages I can gather multiple titles, see their similarity between languages. With the New Look, language switcher became less accessible, though gathering titles by hovering still works there. Also this new dropdown-based language switcher seems either to require tricky CSS features or JavaScript. Will it make problems for simplistic browsers like w3m? _Vi (talk) 17:48, 20 May 2022 (UTC)

I find the language switcher the worst of both worlds of the two variants in the old interface. It can be annoying to scroll through 200+ languages in an idiosyncratic ordering (for example, كوردی [Kurdi in Perso-Arabic script] is filed under S for Sorani), but at least I can see them all and preview the name of the article in various target languages. With the drop-down menu in the old interface, I get the languages grouped geographically, and I can also search for a specific language, with the system recognizing many name variations. The new interface gives me a drop down menu with all 200+ languages in the same idiosyncratic order, with no geographic grouping and no ability to search for a specific language. LincMad (talk) 22:28, 25 May 2022 (UTC)

I am primarily an active user on the Japanese Wikipedia (now defaulted to vector2022) and I agree with you completely. Why doesn't this use the blank spaces on the left and right? No need to hide buttons and functions everywhere just to make the page look hollow. As for the other features, there are so many problems with the new Vector. I definitely want the old version to remain. I will continue to use it and not the new one. --Sugarman (talk) 07:14, 6 July 2022 (UTC)


 * Hello @Sugarman. The space on the right are blank only temporarily. As you can see on our newest prototype, on the left, there are the sidebar and the table of contents, and on the right, there are some links pulled out of the sidebar.
 * As for "No need to hide [...] just to make the page look hollow" - on our pages, we explain why hide some links and functionalities. We never argue that we want the page to look hollow. We work to make the page look intuitive and welcoming. Entry points to advanced collaboration need to be clear, and not numerous.
 * Unless you are an advanced user already. We realize that advanced users may need to access specific links with one click. We encourage you to describe (some day when you decide to spend some time on it) all the problems you would like to see solved. Perhaps this may be addressed by adding/adjusting gadgets and user scripts. SGrabarczuk (WMF) (talk) 23:50, 4 August 2022 (UTC)

Hey, thanks for all of this feedback. I wanted to share a few different ideas that have come up over the past month or so as we've heard from various editors (including yourselves) about language switching.

1. For people who primarily switch between two languages: once you switch languages we could show a language link next to the language button, leading back to the language you came from. This would be somewhat similar to what happens on Commons and Wikidata when you switch languages. So for example, if you just switched from French Wikipedia to English Wikipedia the page would look like this:

2. For people who are logged-in and frequently switch to many different languages: we could make the language menu pinable to the sidebar, so that 9 (or even more) language links are exposed directly on the page at all times. We are already planning to make the tools menu and the main menu pinable in this way.

3. For people who are logged-out and frequently switch to many different languages: we could experiment with exposing more language links directly on the page. We've started exploring this in this task: https://phabricator.wikimedia.org/T301787. Depending on how many language links we wanted to expose that could look similar to the screenshot above with the link to French (plus one or two additional links), or could be more of a dedicated toolbar for language links: AHollender (WMF) (talk) 16:04, 15 August 2022 (UTC)

Feedback on ToC functionality
Hello,

I’m not sure how far you are in the development of the new table of content functionality, but I was looking at this prototype and noticed a potential problem. Here the ToC is on the side and that’s a good thing, but the ToC in the text have also been deleted and that’s not much a good thing. When there is a big infobox, the in-text ToC compensate partly or totally for it, hence the page arrangement take it into consideration for the position of the images. Now if you delete it, all the text will go up, along with the images, but the images can’t always follow, because the infobox, so the right-aligned images are going to pile under it, while the left-aligned will reduce the text to a very small column between them and the infobox. On fr:wp, infoboxes are very widely used, so deleting the in-text ToC is going to break the page layout of most articles (and rather probably upset the community). So I’d suggest that, whatever you do with the ToC, to not delete the in-text ToC until there is also a functionality to move the infobox outside the text too (that would be great by the way, as infoboxes always cause difficulties with page layout). --Runi Gerardsen (talk) 09:30, 7 February 2022 (UTC)
 * I would like to add myself as having this same concern about images. At present, image placement in many articles was determined by this factor of the TOC being inline, sometimes offsetting the issues of long infoboxes and allowing the first image in the first section to be right-justified (like anyone with any experience in professional publishing, I really hate left-justified lead images as they break up the flow of the text by interposing themselves between heds and text. Similarly, I try to maintain alternation in the justification of images since that mirrors the sweep of our vision and makes text with images easier to read (but of course you don't do this when it creates other layout issues). When this is deployed, a lot of articles are going to suddenly have image placement issues at the top that didn't previously. And this will probably make a lot of people very angry. I can see the need for the sticky TOC but I think it would still be better as something that could be toggled there from its current position while reading depending on how the user prefers it in an individual article. Daniel Case (talk) 05:50, 29 April 2022 (UTC)
 * What if we kept both the inline/in-text ToC and the sticky/sidebar ToC, but only display the latter when the user's scrolled past the former? A user preference could be added that forces the latter to always (or never) be displayed. I agree that the situation with images is a PITFA, but I really don't want to give up the sticky ToC either… OmenBreeze (talk) 00:43, 6 July 2022 (UTC)

I'm not sure, but until I manually switched back to "Vector legacy (2010)", then again to "Vector (2022)", ToC section was absent completely (neither new-style nor old-style). Also maybe, like with the language switcher, there should be [temporary] notice about ToC having moved to the left where it was previously? _Vi (talk) 17:57, 20 May 2022 (UTC)

Left margin menu pushes down content
I normally use Monobook, but happened to get into the new Vector. Odd experience. The search box was absent and I had to scroll down for the content. I now see that you are supposed to click the magnifying glass to get the search box. OK. But the scrolling?

It seems the new Vector tries to guarantee wide enough space for the content. Perhaps that's what people surfing with maximised windows expect, but if you have a narrower window, is that really optimal? To get the left margin menu to the left of the content, I need a window some 1000 px wide. This "minimum" width gives me lines of about 100 characters, while I've heard reading is easiest at 47–72 or something like that. I like to have several windows open in parallel, and a narrower windows makes them fit better.

Anyway, if one's browser window is narrow, for whatever reason, does the empty space to the right of the margin menu really give the best possible experience? Is the 100 char width something that needs to be guaranteed for those planning layout of individual articles? (This experience is with Firefox 91.7.0esr on Debian.)

–LPfi (talk) 20:07, 17 March 2022 (UTC)


 * Hello @LPfi, since your comment, we've introduced the new table of contents, the grid system, and we've improved some issues with margins. What do you experience now? Have the issues you described changed?
 * "I had to scroll down for the content." - do you still need to do that? if yes, what do you see that you need to scroll past? It's the sidebar (the left menu) taking the full width, isn't it?
 * Generally, we try to accommodate Vector 2022 for use cases such as yours. However, with screens narrower than ~1000px, we enter the territory of "should V22 be responsive" which is an area of controversies. We've been receiving contradicting voices, and it'd be a good topic for a separate community discussion. SGrabarczuk (WMF) (talk) 00:55, 5 August 2022 (UTC)

I hate the new TOC
I was directed here from T273473.

That left-of-the-article TOC is a horrible nightmare. I absolutely hate it. I would seriously avoid any website that forced it upon me. Can't scroll it out of sight, can't collapse it, can't disable it, takes up too much space, I hate it I hate it I hate it. This was the reason I switched back to Vector classic on beta cluster. (and if Vector classic gets it too I'll switch to Monobook, Timeless or just murder it with a userscript) I'm not much of a fan of Vector 2022 (but it's not a lost cause, just needs work), but this TOC pushed me over the edge.

As a personal note: I rarely use the existing TOC. But I can scroll it out of sight so it doesn't bother me. If the TOC went completely missing tomorrow, I wouldn't miss it. Having this big, (to me) useless thing that contrasts with the main content (it's much darker) permanently in my field of vision greatly annoys me. And because of the fixed position, my banner blindness fails to kick in. This results in pure hatred for something that, on the face it, could seem innocuous. Alexis Jazz (talk) 16:25, 19 April 2022 (UTC)
 * I was not "directed" anywhere, I blundered onto here after finally finding information about this new skin. And let me be clear, APART from the ridiculous handling of the TOC, the new skin is great, precisely BECAUSE, before the TOC-debacle, this skin allowed me to get more of the article on the screen, and allowed me to hide the standard list of menu choices that I only need 0.something % of the time.


 * So, please, Please, PLEASE make that TOC hideable! It's perhaps (!) a great default for newbies, but it's a bloody nuisance for us who usually never use the TOC, and if we do, we know where to find it! Autokefal Dialytiker (talk) 21:49, 25 April 2022 (UTC)
 * I totally agree. 185.53.157.151 08:13, 26 April 2022 (UTC)
 * @Autokefal Dialytiker, right, it's not that easy to get here. We'll put link to the project page on the list of available skins in preferences. The task is documented as T307113. SGrabarczuk (WMF) (talk) 15:25, 28 April 2022 (UTC)
 * Hey @Alexis Jazz - thanks for talking to us. It’s good to hear you were using Vector 2022. I hope that you will switch back to it. In terms of the table of contents, you raise good points. A lot has been happening since you wrote your comment, so my answer is longer than it would have been last week.
 * The first version of the design was based on the feedback we got on our previous prototypes from readers and editors (see in-person reader & editor testing and on-wiki community testing).
 * That said, we have not yet made the design final. We are working on different ideas for the visual design of the entire site. We'll make the main content of the page be the primary focus of attention, even when other navigational elements (such as the ToC) are present. If you’re interested in following along with that work, most of it will be tracked on T301780 and in subtasks of that ticket.
 * We are also considering the way the ToC will display at smaller resolutions (T306904, T306660) and looking into some options for collapsing it that could work for wider screens as well.
 * As you can see, people like you who have chosen Vector 2022 individually share a lot of feedback with us now. T307004, T306562 are some examples on things we are or will be working on.
 * In the meantime, we will be A/B testing the ToC on the pilot wikis. Our hypothesis is that the ToC will decrease the amount that people have to scroll to the top of the page to switch to a different section. The design might also vary once we have the results of the test.
 * Since these changes might take a little while to reach the beta cluster, we would also encourage technically-skilled folks to set up a script or gadget to make a temporary solution.
 * And... yeah, subscribe to our newsletter, join our office hours (tomorrow or later) and talk to us more. Thank you! SGrabarczuk (WMF) (talk) 15:23, 28 April 2022 (UTC)
 * SGrabarczuk, here's another thought: reverse. It's not a long page, but that TOC is so bloody huge a full HD display isn't enough to read any of the actual page content without scrolling. Alexis Jazz (talk) 01:39, 1 May 2022 (UTC)
 * Right, right. Let's just take a look at pl:Gramatyka języka fińskiego. I mean, this is an edge case, and as such, it's not that critical. From what I know, all TOC sections aren't uncollapsed by default, and you need to make an effort to see the full TOC. Is this your experience, too, @Alexis Jazz? SGrabarczuk (WMF) (talk) 22:45, 5 May 2022 (UTC)
 * SGrabarczuk, sorry for being possibly unclear. It was just a thought about the classic inline TOC which is disproportionally huge on Wiktionary, so it's something to think about when designing a new TOC. On the Gramatyka page on plwiki you at least get the intro without scrolling and the page actually is very long, so it's understandable the TOC also gets big. I've taken a look at the CSS (should have done that sooner) and simply disabling "position:sticky" stops the new TOC from being so infuriating. IMHO that should be the default, or at the very least, proper research should be done into this. Not only to determine by majority vote what users prefer (I wouldn't be surprised if sticky wins a binary majority vote) but also how crazy either option can drive users who don't like it. Pleasing a majority is no good if it causes a minority to be greatly aggravated. While I personally can get around it using technical means, that isn't true for most people. I'll also note that the experience on devices that are primarily controlled with a touchscreen may very well be different. With a keyboard, scrolling back up to the TOC is nearly no effort. Just press "home" or hold "page up". With a touchscreen, not so much, so I can see why sticky might have a greater appeal there. Alexis Jazz (talk) 07:11, 6 May 2022 (UTC)
 * What TOC? I don't get any such thing. Betaneptune (talk) 17:36, 25 May 2022 (UTC)
 * 1000px still seems like not enough for hiding the ToC. e.g. 1280 width on a rather large 16:10 projector screen and it is cumbersome and distracting. The floating option to hide it should definitely be implemented (closer to the left edge of the screen, hiding the TOC should make the content padding completely symmetrical left/right!) as that'd actually make Vector 2022 usable. Having it automatically (temporarily) pop out on mouse over would be quite nice, with a click to make it "stick" until clicked again, like a hamburger button you can hover over. For the record, I use Vector 2010 on smaller displays regardless of DPI, as well as high DPI larger screens, and Monobook on everything else. -αβοοδ (talk) 18:05, 29 July 2022 (UTC)
 * 100% agree. Football Lab (talk) 09:14, 26 June 2022 (UTC)

Watchlist icon
Schierbecker wrote: "The watchlist icon too closely resembles a hamburger menu button. I can see many clicking the button thinking it is a dropdown menu. Some may lose unsaved edits after clicking it."

I completely agree, but not really because it resembles a hamburger button but because it's sandwiched (no pun intended!) between dynamic menus. If there was the dropdown arrow next to the interlangs, alerts and notices buttons just like the personal menu, it would communicate more clearly that the watchlist button is a simple link and not a menu. Nardog (talk) 02:38, 21 April 2022 (UTC)


 * Thanks for this comment, @Nardog. We'll think how we could improve this. SGrabarczuk (WMF) (talk) 23:55, 27 April 2022 (UTC)
 * Information on the design process that led to the current icon can be found here:
 * https://phabricator.wikimedia.org/T297979
 * Nardog is already involved in that task. It's probably best to add this feedback there, as not all designers are reviewing this talk page. Jdlrobson (talk) 17:01, 6 July 2022 (UTC)

"Beginning" is confusing
More feedback: when I was at Gotcha journalism just now, I became confused because there appeared to be a section titled "beginning", which I assumed covered the early history of the term. It took me a minute to figure out that that wasn't referring to a section but rather a way to scroll to the top of the page. Many other articles are going to have a similar problem, since we often begin with history sections that might reasonably be titled "Beginning" for early history. &#123;{u&#124; Sdkb  }&#125;  talk 22:42, 27 April 2022 (UTC)


 * @Sdkb - good catch! This is something we discussed quite a bit internally in order to finally settle on beginning, although I agree that it's still imperfect. Previously we were using "introduction".  The issue there was that many articles have "introduction" as the name of their first section, causing duplication.  Other options we were considering were location-based (back to top, beginning of page, etc).  We are welcome to ideas on how to make this clearer.   OVasileva (WMF) (talk) 09:05, 28 April 2022 (UTC)
 * The name used by wikipedians? Lead section in English, résumé introductif in French, etc (Q10966628) Pyb (talk) 11:07, 28 April 2022 (UTC)
 * On Translatewiki.net I found "Début" for fr.wiki and "Inizio" for it.wiki (on it.wiki we use also "Incipit" or "Introduzione", see T306990). Patafisik (talk) 15:09, 28 April 2022 (UTC)
 * @OVasileva (WMF), did you consider different design approaches in addition to different names? If the word had been accompanied by something like Font Awesome 5 solid caret-up.svg, it might have been a lot clearer. I also think there's some benefit to matching the terminology we already use as editors ("lead section" or "introduction"), since that makes it easier for newcomers. The Wikipedia articles that currently have "Introduction" as their first named section should not—they should be tagged with w:Template:Overview section. &#123;{u&#124; Sdkb  }&#125;  talk 20:16, 28 April 2022 (UTC)
 * Bumping @OVasileva (WMF). &#123;{u&#124; Sdkb  }&#125;  talk 17:16, 6 July 2022 (UTC)
 * Just leaving a note here that we're still watching this conversation and considering different options, but haven't made a decision yet.  OVasileva (WMF) (talk) 13:58, 11 July 2022 (UTC)
 * I think using the article title would make the most sense, as the title is the uppermost heading in the article. That way the header that the reader arrives at always matches the one they've clicked on. (I'm sure "Beginning" is better than "Introduction," but it's not unheard of as a section title either: e.g. Creolization, Ashikaga shogunate, History of Carthage. Is there any way to determine how often it's used?) Arms &#38; Hearts (talk) 19:35, 29 May 2022 (UTC)

I think "Top" would be less confusing and generally make more sense as that seems to be the common English term for the top of the page. 132.170.199.112 19:32, 22 June 2022 (UTC)

Table of contents below sidebar just doesn't work
On a broader note than the two pieces of feedback above, I have to say that my experience so far with the new table of contents has been really frustrating. As an editor, I use lots of the links in the left sidebar quite frequently, so I don't want to collapse it (and even if I did, the way it persists in whatever state you leave it in means that every time I used it it'd return). But preserving the left sidebar forces the table of contents below it, which is just awful. The number one time I want to use the ToC is when I first navigate to an article, and I either want to jump to a specific section or just to see what sections it has to get an overview. Forcing me to scroll to get to that information is extremely annoying, and if it's kept in the final version, I predict the outcry will be intense. You could resolve this either by retaining the old style ToC alongside the new (which would also solve the sandwiching concerns I've previously raised) or by moving the ToC above the left sidebar. From your previews, I know you've been working on moving some stuff around and introducing pinning, so I hope this will be resolved in future iterations. But the initial version being introduced here is clearly not ready yet. Best, &#123;{u&#124; Sdkb  }&#125;  talk 22:53, 27 April 2022 (UTC)
 * For me it seems the table of contents and the sidebar seems to be two different things. On Wikipedia, I collapsed the sidebar and the table of contents still remain. Tenryuu (talk) 03:09, 28 April 2022 (UTC)
 * I want ToC collapsed too. But there is no way to do it. It uses almost 1/3 of my screen and makes reading very difficult.- Nizil Shah (talk) 05:32, 28 April 2022 (UTC)
 * Same here. 14" Screen, collapsed sidebar menu, open only when needed. With the new TOC I cannot collapse the sidebar, it's just a toggle between navbar and TOC. I appreciate the effort and that it's a first attempt, but it definitely should be optional. And yes, I was involved in feedbacks and testing earlier. Regards Elya (talk) 14:24, 29 April 2022 (UTC)


 * +1, the TOC should be accessible from the top of the page, and collapsible (vertically; also horiz if it is making the sidebar too wide - many pages have section heads that are quite long). Sj (talk) 17:35, 2 May 2022 (UTC)
 * @SGrabarczuk (WMF) and @OVasileva (WMF), neither of you have replied here. This is a major concern, and I predict that if it is not addressed, it may single-handedly prevent the community from being willing to accept New Vector. &#123;{u&#124; Sdkb  }&#125;  talk 17:14, 6 July 2022 (UTC)
 * Hi @Sdkb - thanks for the ping! Currently, we're working on making the ToC collapsible, especially on narrow screens (T306660).  Collapsing it would allow for access further up in the page, but won't completely solve the issue you're describing.  To make using both the sidebar and the table of contents a bit easier, we are planning two things.  For logged-out users, we plan on collapsing the sidebar by default so that the table of contents will be shown further up in the page.  We are also planning on separating the tools related to pages in a separate menu.  This will significantly shorten the space for the sidebar, and create a clear definition between which tool acts on the page as a whole, and which one acts only on the page itself.  In this example, this puts the ToC above the end of the introduction section, which is higher than the previous ToC location (admittedly, this will not be the case for all articles).
 * Prototype_of_table_of_contents_and_tools_menu_for_desktop_Wikipedia.png
 * OVasileva (WMF) (talk) 14:07, 11 July 2022 (UTC)
 * Thanks for the reply, @OVasileva (WMF)! Moving the tools elsewhere (ideally to a Twinkle-like menu) is something I certainly support and have been trying to set up since the 2020 revamp, and it would help with this. Your screenshot appears to be from a standard resolution display rather than a widescreen display, so I can't tell whether it's going to help enough to ensure that the ToC will always be visible on a normal monitor with neither it nor the main menu collapsed. Getting to a point where that's the case will be essential for getting community consensus.
 * Is there a reason you don't seem to be considering placing the ToC above the main menu? &#123;{u&#124; Sdkb  }&#125;  talk 23:49, 13 July 2022 (UTC)

About Google Docs and Zoom
Thank you for the invitation I received for tomorrow's videcall since I was an interface admin and a developer! but sadly I cannot participate since I don't use Google Docs or Zoom for security reasons (partially related: ).

I don't know if it could be useful but maybe in the future you may consider to land the doc on the wiki itself, or using Etherpad when realtime is needed.

To drop Zoom, maybe I can propose Jitsi Meeting that is gratis and libre and supports streaming on social network to support large audience. (Also Wikimedia Meet deserves a try and some feedback). Valerio Bozzolan (talk) 15:38, 28 April 2022 (UTC)


 * Hello @Valerio Bozzolan. I understand your concerns and thank you for the language you use. I do appreciate that. As you may have realized, it isn't without a reason why we use these particular tools/platforms.
 * Google Docs are used by the Foundation as the default tool for making internal notes and docs. We might, for the purposes of the office hours, replace it with Etherpad. There's a problem with the translations, though. Asking translators to update just one word, and waiting until they've done that, could be troublesome. This is why I can only commit to replace this if we make more changes to the announcement. (By the way, the announcement is fully standardized and translated into 16 languages, some of which use declination or are not written in the Latin script.)
 * We need our office hours to be technically (platform-wise) predictable. Although Jitsi is open source and Zoom is not, the latter is more effective. It has been widely used for online meetings in the movement. It's been used by the WMF for office hours with the CEO, Maryana; it's been used by affiliates. There are hundreds of Wikimedians who at least once have participated in a Wikimedia meeting on Zoom. We know how to provide live translations there. Jitsi, on the other hand, is less popular, and we'd have to learn how to support live translations, including more trainings organized specifically for our meetings.
 * We may consider having office hours on IRC. Frankly, I have a feeling that since the migration from Freenode, IRC has been more and more marginalized, but we could give it a try.
 * I'm curious what other Wikimedians watching this page think. Add your comments! SGrabarczuk (WMF) (talk) 22:15, 5 May 2022 (UTC)
 * Just asking for an understanding that Google Form and Zoom are a bug, not a feature, to participate in a Wikimedia project. A bug that deserves a long-term fix. Valerio Bozzolan (talk) 15:57, 7 May 2022 (UTC)
 * I appreciate these are standard across parts of the Foundation. And agree w/ Valerio this is a bug, not a feature. Perhaps it's time to revisit this across the org. :)  We should be using tools that can be constantly used and deployed by communities for events, workshops, office hours, talks without sending traffic through commercial servers.
 * Text: Google makes some very wiki-spirited tools (they did absorb JotSpot back in 2006) so it's stayed around for a while. But we simply must stop using it as a crutch that keeps us from using and being delighted by notetaking on our own platform. Our collaborative platform for drafting and discussing documents. Our versioned, searchable platform.
 * Video: I too have to use Zoom sometime, but I'm always surprised and a bit dismayed when a Wikimedia meeting uses it! Jitsi is stable, widely used + repackaged, easily modded and forked, and we host a lovely instance on the WM cloud. [We also regularly use BigBlueButton for larger audiences.] It makes it easy to name a persistent rooms, embed it it in other places or tools (see Jitsi-as-a-service + Brave Talk these days), &c. We should be thinking about how to better use video streams in our projects, and using this framework as we do so. Sj (talk) 12:54, 14 May 2022 (UTC)
 * Thanks @Sj and @Valerio Bozzolan.
 * First of all, I really hear what you're saying. Perhaps you're right, Google and Zoom may be bugs - it's definitely not up to me to decide. "Perhaps it's time to revisit this across the org. :)" - I'm grateful that you specifically used the words "across the org". That's way wider than just Olga and me (people who organize our office hours), or Community Relations ("technical liaisons" so to speak), or Movement Communications alone. If it's about the standard, then it needs a broad agreement.
 * @SJ, do Jitsi or any open-source alternatives provide the speech-to-text functionality and parallel voice tracks for live translators (interpreters)? I'm asking because each time we have a meeting, there are people who need the speech-to-text functionality . Unfortunately, we haven't been able to provide the live translation support yet. We're still working on it, and it seems we may have found a solution.
 * SGrabarczuk (WMF) (talk) 15:55, 6 July 2022 (UTC)
 * SGrabarczuk:
 * 1. We should change the standard [though there seem to be many even within one org!], but I only mentioned that to suggest that none are set in stone. :) As this thread is about these particular discussions, I hope we can try a different standard for these sessions, or understand what prevents such a change.  If it is purely a matter of accessibility features, that would make a phabulous ticket even if it is not yet known who could set them up.
 * 2. Yes they do! Other collaborative orgs w/ similar issues of language equity use jitsi regularly. There are solutions or workarounds for both. [also, to the point of "supporting essential infrastructure for free knowledge", our engagement would certainly help make them better for all.]
 * speech to text: Google Voice integration seems to be there, and a number of open-source s2t services that are not quite comparable. You can see the range of Summer of Code projects + community submissions scratching their own itches in the jigasi repo.
 * remote simultaneous interpretation: the most recent solution (for a single language, letting you tune in or out of the raw audio and into a translator's audio channel) is use by May First (which we should work more closely with on choosing technology stacks, frankly) and is maintained here. There are improvements, and pushes to integrate into jitsi core, both of which could be facilitated by small technical bounties or large expressions of interest [like Wikimedia indicating this is a crucial feature for us]. Sj (talk) 02:37, 7 July 2022 (UTC)


 * @SGrabarczuk (WMF), I will not participate in any forum that is not public. Why the wmf foundation wants to share information via Zoom, a for-profit corporation which provides no guarantee of privacy, is anyone's guess. We have been using wiki-code for discussion since 2001, why this change?
 * I apologize if you find my message above irrespecutful, but this represents the views of many. Ottawahitech (talk) 18:26, 13 June 2022 (UTC)
 * @Ottawahitech, above, you can find explanations on why we (the Web team) are using Zoom now. Are you also asking why we have any voice online meetings in general? SGrabarczuk (WMF) (talk) 15:57, 6 July 2022 (UTC)

Instant jumping vs. animated scrolling for table of contents
As you're polishing up the table of contents, one thing it'd be nice to consider is the behavior when you click on a section in it. Currently, it instantly jumps to that section, but I think it'd be better if it instead did a very quick scroll (maybe a quarter of a second). This would help readers to more easily understand what's happening when they click the link, and to get a better intuitive sense of what the article contains by seeing it flash by. Would that be possible? &#123;{u&#124; Sdkb  }&#125;  talk 02:37, 30 April 2022 (UTC)


 * Bumping @SGrabarczuk (WMF) and @OVasileva (WMF). &#123;{u&#124; Sdkb  }&#125;  talk 17:12, 6 July 2022 (UTC)

Trouble With Zooming In
My vision is poor so I usually zoom to 200% on my browser and it is no problem. With the new skin that same magnification causes the sidebar to take up the top of my screen and I can't see the title of the article and know what page I'm on without scrolling.

Wikistories
Will Vector 2022 be influenced by Wikistories? -- NGC 54  ( talk |  contribs ) 10:09, 6 June 2022 (UTC)


 * @NGC 54, what do you mean by influenced? SGrabarczuk (WMF) (talk) 22:18, 14 June 2022 (UTC)
 * @SGrabarczuk (WMF): If Vector 2022 will be adapted for (compatible from a design perspective with) Wikistories. -- NGC 54  ( talk |  contribs ) 19:06, 15 June 2022 (UTC)
 * @NGC 54, definitely. All the projects that currently are being built are compatible with or neutral to Vector 2022. SGrabarczuk (WMF) (talk) 16:47, 30 June 2022 (UTC)

Language switcher opt-out
The new language picker is a deal breaker for me as an active editor who is working with a very diverse array of topics on Wikipedia. I write about Māori language, Japanese geisha, Taiwanese literature, Inuit cuisine, Paraguayan instruments, Vietnamese temples, Algerian regions, Berber cuisine, Arabic professions. I write articles that compare dozens of cultures or languages.

I need a way to hover over the list of languages to see the name of the page in a different random language (which can be anything from Korean to Twi). I need to be able to open 50 language editions very quickly to estimate if any of them have good illustrations or any new literature on the topic that I am working on. I often read the same article in 4 languages simply because I can read in a lot of languages and I am wondering which language edition has the best article. The workflow with the new language picker is tremendously stunted.

The main idea of the new interface seems to be making the page width more narrow. With that, there is a lot of free space at the sides, and I would like to propose putting a full list of languages there, as an option. Le Loy (talk) 00:29, 13 June 2022 (UTC)
 * Yes, I agree, the decision taken now does not help advanced editors work in projects, but hinders them. I think we need to make a separate setting for the "always open" list. The problems of this list have still existed since sorting was removed. Iniquity (talk) 15:43, 14 June 2022 (UTC)


 * --Wdpp (talk) 11:47, 3 July 2022 (UTC)

Old version

 * Moved from Topic:Wxcz2an2ck4s4cdy

After these changes are made, can I still use the old settings? Ilovemydoodle (talk) 09:26, 13 June 2022 (UTC)
 * Yes Ilovemydoodle, legacy Vector will be available and you will be able to use it as your skin. SGrabarczuk (WMF) (talk) 12:24, 14 June 2022 (UTC)
 * Why does have to be called “legacy”? legacy implies that something is outdated, inferior, no longer supported, none of which apply to Vector "legacy". Maybe instead, you could call it "advanced", "expert", or "classic". – Ilovemydoodle2 (talk) 17:48, 20 July 2022 (UTC)
 * @Ilovemydoodle2, the motivation is purely technical. This is because it's "frozen". The Wikimedia Foundation will not develop it - there will be no actively built version of Vector parallel to Vector 2022. SGrabarczuk (WMF) (talk) 20:46, 20 July 2022 (UTC)

Irish language Wikipedia and Vector 2022


Hi there. I'm w:ga:User:Alison - admin and bureaucrat on the Irish language Wikipedia. I'd be remiss in not providing feedback, I think, so here goes.


 * I see other folks pointing out the massive amount of whitespace / padding in the left side navbar which is squeezing out the actual article text on the right. On our wiki, it really seems significant. IMO, article is all, and we seem to be sacrificing actual content real-estate for ... what, exactly? Yes, it looks 'less cluttered', but there's actually less content - especially for those of us who both browse and edit on laptop screens.


 * On the top tab section (which is otherwise quite nice), you can see the Plé (Talk) and Léigh (Read) are scrunched together with no separation. I18n bug, maybe?


 * The main image and title have lost their localization and now show "Wikipedia" instead of "Vicipéid" - this could just be an image localization / config issue. Could someone point me in the right direction, maybe? I did the original, later-font localization for our wiki, some years back, so happy to dip in and fix :)

Le gach dea-ghuí (best regards),

-- Allie Alis o n  ❤ 16:17, 22 June 2022 (UTC)


 * multilingual Wikipedians: during redesigh include current non-english desighs for evaluation, including spanish, french and german. They have good ideas and bad ideas... 0mtwb9gd5wx (talk) 01:10, 23 June 2022 (UTC)
 * The "PléLéigh" issue looks like it's T309223, a known issue. Until it is fixed in MediaWiki, try updating your browser(s) – the issue occurs if your browser doesn't support a certain relatively new feature. Rummskartoffel (talk) 21:59, 23 June 2022 (UTC)
 * Hey there! Regarding logos https://phabricator.wikimedia.org/T244486 is what you are looking for - basically every logo needs to be recreated. You can request one on that ticket to be prioritized higher or find information about creating new ones.
 * Regarding sidebar whitespace I am not sure I understand. The extra padding is for the table of contents underneath the sidebar. You say it's squeezing article text on the right but in your screenshots the Vector 2022 screenshot shows more of the article text. I can see the description section heading for example.
 * I can confirm the PléLéigh issue is a bug and will hopefully be fixed soon.
 * Hope this is helpful. Jdlrobson (talk) 01:02, 1 July 2022 (UTC)

wordmark no longer appears after upgrading to MediaWiki 1.38.1, style bugs
After upgrading to MediaWiki 1.38.1 from 1.36.1, the wordmark no longer appears next to the icon in the upper left. If the window is wide enough, the 150px space for the wordmark is reserved but is empty. When you make the window wider past a certain width, the coloring behind the sidebar also vanishes. This happens with Vector 2010 in both legacy and non-legacy mode and in Vector 2022. The wordmark image is an svg that has not moved and still has correct permissions Queernix1028 (talk) 19:43, 22 June 2022 (UTC)


 * What is the value of wgLogos in your LocalSettings.php? Jdlrobson (talk) 14:22, 29 June 2022 (UTC)

$wgLogos = [ 'icon' => "$wgScriptPath/images/arcc/logo.svg", '1x' => "$wgScriptPath/images/arcc/logo.png", 'wordmark' => [ 'src' => "$wgScriptPath/images/arcc/wordmark.png", '1x' => "$wgScriptPath/images/arcc/wordmark.svg", 'width' => 150, ], ];
 * It previously worked with wordmark src set to the svg file, but now neither that configuration nor the one above work. Queernix1028 (talk) 14:32, 29 June 2022 (UTC)


 * I believe you need to set a height on the wordmark. Jdlrobson (talk) 00:55, 1 July 2022 (UTC)

Language links on Wikidata are right at the bottom of the page
I've enabled the new theme (Vector 2022) globally on all wikis. I generally like the new interface. However when I am on wikidata, previously the interlanguage links were on the right. (Where an infobox usually goes on a wikipedia page) Now they are right at the bottom of the page! Some wikidata pages are massive, and having to scroll all the way down to the bottom of the screen to do the thing I do most frequently on wikidata (add new language links) is a real pain. Please can you move the language links on wikidata back to the top (top right) of the page? - Rooiratel (talk) 14:25, 23 June 2022 (UTC)


 * Hello @Rooiratel. Thanks for your opinion. Are you talking about the desktop view? What's the resolution of your screen? I've tried to narrow my window down and change its width, and it seems that the width thresholds when the interwiki links go from the bottom to the right are the same. Is there any setting you use that may make your experience different? SGrabarczuk (WMF) (talk) 23:50, 27 June 2022 (UTC)
 * Hi this is for the desktop view. I am seeing this behaviour on my 1080p laptop screen and my 1440p desktop screen. I haven't used the mobile view, so can't comment on that. - Rooiratel (talk) 06:32, 28 June 2022 (UTC)

Infobox element alignment is mangled in mobile view
Maybe I'm doing something wrong, but when I click on "Mobile view" with Vector 2022, many of the infobox elements are misaligned. Many elements that should be centered are left-aligned, and many elements that should be left-aligned are centered. At least that's what it looks like for me in Chrome for Mac OS at this page. Jonesey95 (talk) 02:57, 24 June 2022 (UTC)


 * Wow, that looks odd. Thanks @Jonesey95 for reporting this. Right now, I only have one question - why do you use the mobile view and Vector 2022 mixed together? Minerva is dedicated for mobile, and Vector 2022 is dedicated for desktop. Having these two at the same time is bold and original :) SGrabarczuk (WMF) (talk) 23:08, 27 June 2022 (UTC)
 * I was just doing some very beginner-level QA testing. Editors do all sorts of ridiculous things, so I try to do some QA testing by doing ridiculous things. If you want editors to use Vector 2022 for desktop-only and Minerva for mobile-only, then make the "Mobile view"/"Desktop view" link at the bottom of the screen switch between the skins. Meanwhile, I'll be over here in legacy Vector where I can fill my browser window with content.... Jonesey95 (talk) 01:15, 28 June 2022 (UTC)

Using the mobile domain with the Vector skin invokes a special mode with lots of odd behaviour. It's not part of this project but will hopefully get fixed some day. Jdlrobson (talk) 02:30, 28 June 2022 (UTC)

"Related articles" appear to be missing
I do not see the "Related articles" section at the bottom of the mobile view. I don't really care, but since the "Principles" section of this page says "We do not remove any functionality", I thought I'd mention it. It makes me wonder what other functionality has been removed, and whether this principle is really being followed in a systematic way. Jonesey95 (talk) 03:02, 24 June 2022 (UTC)

RelatedArticles appears to be working fine to me. I see it on Minerva. What do you mean by "at the bottom of mobile view"? The scope of this project is the desktop site so no changes to the mobile domain have been made.

RelatedArticles does not show on the skins of certain websites and has not shown on Vector or Vector 2022 unless the community has explicitly requested. See T144812, T181242 and T278611 for example. Jdlrobson (talk) 14:59, 24 June 2022 (UTC)
 * I think this is my mistake. I was comparing this (default mobile view on en.WP) with this (Vector 2022 mobile view) and assuming that the default mobile view used some version of the Vector skin, but I think that is not correct. Jonesey95 (talk) 16:38, 24 June 2022 (UTC)

Ah okay. This mode is only accessible by a special URL and is not being worked on as part of this project. Thanks for taking the time to explain! Jdlrobson (talk) 02:28, 28 June 2022 (UTC)

非常に見にくい
日本語で失礼します. 本日ごろから日本語版ウィキペディアのスキンに変更があったようですが、 などの変更のせいで、余計見づらくなったような気がします. 可能であれば改善するか、もしくは変更前のスキンに戻して欲しいです. イカしたイカ (talk) 08:38, 24 June 2022 (UTC)
 * 1) 文字の大きさをブラウザ側から変更できない(Safari使用).
 * 2) そもそも標準の文字サイズが大きすぎる.
 * 3) 目次が項目名の横に位置が変わったせいでアクセスが煩雑になった.
 * 4) Infoボックスが大きすぎる


 * 感謝します、@イカしたイカさん.
 * First of all, you don't need to apologize for writing in Japanese. We welcome comments in any language.
 * Would you like just to change the default font size? Or would you be able to zoom in and out, and see the font size adjust?
 * Do you think making the text line wider and keeping the default font size would fix the problem?
 * Why do you think access is more complicated now? Our motivation was to reposition the table of context to make it more accessible. What do you think is not working?
 * Do you think the problem is related to the default font size?
 * まず第一に、あなたは日本語で書いたことを謝罪する必要はありません. どんな言語でもコメントを歓迎します.
 * デフォルトのフォントサイズを変更しますか？ または、ズームインおよびズームアウトして、フォントサイズが調整されるのを確認できますか？
 * テキスト行を広くし、デフォルトのフォントサイズを維持することで、問題が解決すると思いますか？
 * なぜ今、アクセスがより複雑になっていると思いますか？ 私たちの動機は、コンテキストのテーブルを再配置して、よりアクセスしやすくすることでした. 何が機能していないと思いますか？
 * 問題はデフォルトのフォントサイズに関連していると思いますか？
 * SGrabarczuk (WMF) (talk) 02:18, 12 July 2022 (UTC)

Please evaluate CJK characters' font size in Vector 2022
For your infomation, the Chinese Wikipedia already has a gadget that increases the font size for a better Chinese reading experience. Japanese and classical Chinese Wikipedia also have such kinds of gadgets. Diskdance (talk) 08:19, 25 June 2022 (UTC)


 * It would be nice if we could integrate these gadgets into new Vector skin directly. This would benefit other CJK and multilingual wikis. Diskdance (talk) 08:20, 25 June 2022 (UTC)
 * Thanks @Diskdance! @AHollender (WMF) FYI :) SGrabarczuk (WMF) (talk) 23:03, 27 June 2022 (UTC)

I think we should create a phabricator ticket for this one. Jdlrobson (talk) 02:29, 28 June 2022 (UTC)

Feedback regarding Vector (2022) TOC
I've had Vector (2022) enabled for a while, and generally like it. However:


 * I don't feel the new way of handling the TOC and side menu is user friendly. It took me a while to notice I could hide the side menu only to raise the TOC up the page, as I assumed it would also hide the TOC since the two are part of the same sidebar. With the side menu visible, I had to scroll much further down than usual to find the TOC on many articles with short lead sections, which undermined the convenience previously provided by the TOC as a way to skip scrolling and quickly navigate to a desired section.
 * It also doesn't help that the new TOC breaks the functionality of Skip to talk, widely used on talk pages on Wikipedia, but I now understand that the change is intended to make that template unnecessary.
 * The prototype linked by others above deals with some of these issues but is still a bit confusing. It's not clear that clicking "hide" on the TOC should result in a menu appearing by the article title rather than just collapsing it like collapsible lists which use the same "[hide]" links; while this behaviour can be learned, it's not clear why the hidden TOC menu button doesn't persist between the search icon and article title when scrolling down, which is what I expected after seeing it collapse to a button beside the article title.


 * The new sidebar is wider to accommodate the TOC, but much of that space is blank so I'm not sure it needs to be quite so wide, particularly as the added width can cause issues such as galleries by default having less space for images per row. I understand the motivation is to limit the characters of text per line, but doing so by padding the sidebar with empty space seems like an unhelpful way to achieve that. Scyrme (talk) 16:57, 26 June 2022 (UTC)


 * I want to chime in about the "hide" behaviour. I noticed the link for the first time right now, tried clicking it and was a confused when it disappeared altogether. I would have expected the link to change to "show" and the table itself to hide. It took me a while to find the icon in the header. I think that if it should behave this way, it needs to somehow be communicated to the user where the TOC goes. Sebastian Berlin (WMSE) (talk) 10:42, 3 August 2022 (UTC)

Merge notification block in the header: notifications and alerts
For me, it has always been a strange decision that notifications were divided into two unrelated blocks and icons with incomprehensible categorization. I forgot about it, but now I'm paying attention again.

Given that we removed the text from all menus, there are now a lot of icons at the top that do not understand what they do. Different blocks of notifications do not help this at all. Maybe it's time to put them in one menu and break it there already? Filters, tabs, whatever :) But at least you won't get confused in the icons.

I personally still (6 years!) do not know what their fundamental difference is. I asked my friends and they don't know either. Iniquity (talk) 17:29, 27 June 2022 (UTC)


 * . The notices are the notifications that are not very important/urgent, unlike the alerts. Merging them would make me unable to found out at a glance if I have any important/urgent notification, and would also overload the notification box, as I receive many notifications. -- NGC 54  ( talk |  contribs ) 22:19, 27 June 2022 (UTC)
 * It seems to me that it is possible to do this with filters and colored marker icons. Or a separate setting for users who really need it. Iniquity (talk) 09:47, 28 June 2022 (UTC)


 * . I agree that the distinction could be clearer, but don't necessarily agree that there should be only one button. Presently, when both are empty the only difference between them is the header text and icon. Both share the exact same two buttons, which link to the same destinations. The text in the box doesn't even distinguish, reading "There are no notifications" instead of "There are no alerts". There isn't even a "help" or "about" link unique to each of them to explain the difference or what gets sent where. If you follow the links to the special page or preferences, it's still not clear which notifications are sent where.


 * Based on the names, I would've assumed the difference would be that alerts are specifically for subscriptions to article alerts, whereas notifications would be for everything else. It makes sense to split them, since alerts would be activity that's less personal to the receiver. "Alerts" would be like a daily newspaper, but "notifications" are more like personal mail. Except this isn't how the system actually functions; messages to the receiver's talk page are placed under "Alerts" rather "Notices", for example.


 * I understand that it may be helpful to filter urgent notifications from less urgent ones, but what counts as urgent or important? Shouldn't that be decided by the user's preferences? It would make more sense to have something like tabs, as Iniquity suggested, to filter types of notifications; this would let that user decide what is important. Scyrme (talk) 22:33, 27 June 2022 (UTC)

Table of contents: Bold format for active section
I really appreciate the new skin and layout. In the beta, the active/current section of the article was formatted bold in the table of contents on the left side. But in the live version, it's regular and black. I find it really, really hard to differentiate between the normal blue titles and the active title, because the only difference is the black vs. blue color. Could you please make the active titles bold again? Thank you! Lhennen (talk) 21:11, 29 June 2022 (UTC)


 * +1 Bold and black would be best imo. L.xschlag (talk) 11:43, 1 July 2022 (UTC)
 * @Lhennen, @L.xschlag - thank you for your feedback! Not sure if you've seen, but we are  currently in the middle of testing some prototypes related to this question.  You're welcome to give us more detailed feedback on the prototype page.  One of the things we're testing on these is the way links should appear within the table of contents (see https://di-visual-design-toc-active.web.app/Otter) for an example.  Currently, our feedback is showing us that people are leaning towards option 2: bold and black so we will most likely be continuing with that option and making the titles bold.   OVasileva (WMF) (talk) 10:08, 4 July 2022 (UTC)

Jawiki has NOT reached consensus on implementing Vector 2022 yet
Jawiki has NOT reached consensus on implementing Vector 2022 yet. Why was it implemented without our consent? AppleRingo777 (talk) 22:01, 29 June 2022 (UTC)


 * Hi @AppleRingo777 - we apologize for the confusion that the deployment process has caused and the lack of clarity from our side.  We are currently working on reading back through our previous communications and clarifying the process and what happened with individual members of the community.  We will to get back to the community with more detailed thoughts and a process for next steps by tomorrow July 1st.   OVasileva (WMF) (talk) 12:04, 30 June 2022 (UTC)

MediaWiki:Sidebar
Hello! I asked a question at the meeting, but I would like to duplicate it here. Will it be possible to control the location of blocks (right or left) through MediaWiki:Sidebar? Iniquity (talk) 15:34, 30 June 2022 (UTC)


 * Hey! We are still thinking through how this would work. Input valued in T306519 ! Jdlrobson (talk) 14:27, 6 July 2022 (UTC)
 * Thanks! :) Iniquity (talk) 16:16, 6 July 2022 (UTC)

Keep the TOC under the main menu as long as possible (Vector 2022)
When the window gets narrower the TOC is moved into a "Hamburger button". But the main menu stays where it is until the window get's quite a bit more narrower. I think as long as the main menu fits, the TOC should stay at its original place. Especially since the TOC behind the "Hamburger button" is quite easy to miss. L.xschlag (talk) 11:30, 1 July 2022 (UTC)


 * This was a bug. I believe it should be fixed by the end of the week. Jdlrobson (talk) 14:28, 6 July 2022 (UTC)

"Move" is the only in the "More" drop down menu (Vector 2022)
I think it's quite odd that the "More" drop down menu most of the time contains only "move". Is it on purpose to make it harder to find for the average user? L.xschlag (talk) 11:35, 1 July 2022 (UTC)
 * , I have two items - the other is an add-on via preferences/gadgets. Unfortunately, I cannot use drop-down menues easily, so getting there in V-2022 is quite a nuisance. Retired electrician (talk) 21:31, 3 July 2022 (UTC)
 * Isn't the behaviour the same here on the other skins?
 * I agree it's not great having one item in a menu, but I think this case is quite rare since on most wikis move privilege is added along with page protection and deletion. There is a trade off here between the complexity of maintaining multiple variants of the skin in different circumstances and what looks best. Here we could add special treatment for the one item menu but we'd need to add additional code complexity and tests to cover it. Hope this insight is helpful. Jdlrobson (talk) 14:32, 6 July 2022 (UTC)

Actions menu overflows when main menu is active (Vector 2022)
When the main menu is active (meaning visible) and the window is quite narrow the actions menu (Read, Edit source, Add topic, View history) doesn't get condensed in the "More" drop down menu, resulting in a very ugly overflow. L.xschlag (talk) 11:41, 1 July 2022 (UTC)


 * @L.xschlag - thank you for your feedback! This should now be fixed, let us know if you continue seeing issues. OVasileva (WMF) (talk) 13:34, 11 July 2022 (UTC)

Audio player issues (Vector 2022)
When pressing play from a wikipedia article (e.g. first clip in Aftermath_(Rolling_Stones_album)), the page changes text colour from black to pale grey. Almost unreadable. This dead time varies from a few seconds to many minutes, probably caused by unsteady connection on my side. I tried opening 2-3-4... windows with the same article, and some windows seem to be stuck indefinitely while others play with minimal (but still annoying) delay. If I press play directly from file description page ( w:en:File:Under_My_Thumb.ogg), it always plays instantly and the text always stays black. Win 10 Home / Chrome 102.0.5005.115 (64-bit) Retired electrician (talk) 19:29, 3 July 2022 (UTC)


 * I've flagged this bug to the developers of Extension:TimedMediaHandler. This is not related to this project. I'll let you know if I hear anything back. Thanks for reporting! Jdlrobson (talk) 16:43, 11 July 2022 (UTC)

Language mix in the interface
Pardon me if this had already been discussed here. It seems that the language of the interface (as set in preferences) mixes up with local-language elements where it shouldn't.
 * 1) My preferences are always "interface=en", and thus I always see "Contents Beginning" in the TOC section - be it Chinese, Russian or Spanish wiki.
 * 2) The pink box above TOC in ru-wiki says "On this Википедия[sic!] the language links are at the top of the page across from the article title. Go to top." In zh-wiki, however, the message is correctly "On this Wikipedia the language links ..." Retired electrician (talk) 21:23, 3 July 2022 (UTC)


 * Thank you @Retired electrician for reporting this. That's odd. 🤔 The source code is:  On this the language links ... - so apparently, something about  isn't working here. But I don't know what yet. SGrabarczuk (WMF) (talk) 16:20, 6 July 2022 (UTC)

Where are the categories?
Hi this is my first time looking at the prototype, so apologies if this question has been answered elsewhere - where are the categories? MassiveEartha (talk) 04:15, 5 July 2022 (UTC)


 * Hello @MassiveEartha. I'm sorry that you felt confused. We don't touch elements such as categories. These prototypes were only created for editors to help us decide on the visual design matters. If the categories aren't displayed in any of the prototypes, then it's definitely unintentional and also irrelevant to what we do. SGrabarczuk (WMF) (talk) 16:02, 6 July 2022 (UTC)

開発者集団は日本語版を軽視していると思われるThe group of developers seems to downplay the Japanese version
日本語版の利用者の一人としては、開発者の集団は日本語版を軽視していると考える. 一つの証拠として開発者からの意見を求めるメッセージが英語だけで書かれていたことを挙げておく. 機械翻訳があるのだから英語と共に日本語を添えることは簡単なことのはずである. それすらせずにVectorからVector2022への変更を強行したことは、一種の文化帝国主義であると評さざるを得ない. As one of the users of the Japanese version, I think that the group of developers disregards the Japanese version. One proof is that the message for the developer's opinion was written in English only. Since there is machine translation, it should be easy to add Japanese along with English. It must be said that forcing the change from Vector to Vector 2022 without doing so is a kind of cultural imperialism.--27.85.205.84 07:17, 5 July 2022 (UTC)


 * Hello 27.85.205.84. Do you maybe know good open-source machine translators working for Japanese and English? I've noticed that Google Translate doesn't work for these languages well. Sometimes it changes words, meanings, and the tone of entire sentences completely. I could write in Polish, my first language, but I'm sure that would be even more difficult. SGrabarczuk (WMF) (talk) 16:15, 6 July 2022 (UTC)

Vector 2022を強要する行為は、開発者が読者を軽視していることの証拠である The act of forcing Vector 2022 is evidence that developers are downplaying their readers.
開発者（の集団）はアカウントユーザーなら自分で好きなスキンを使えるのだから、あまり出来がよいとは言えないVector 2022を強要してっもかまわないと考えているようである. しかし、元々Vector 2022は読者として快適に使えることを考慮していない. 開発者（の集団）は読者がいなければいくら記事を作っても意味がないということを忘れているのだろうか. It seems that developers (a group of people) are willing to force Vector 2022, which is not very good, because account users can use their favorite skins. However, originally Vector 2022 did not consider it to be comfortable to use as a reader. Do developers (groups) forget that it doesn't make sense to write an article without a reader?--27.85.205.84 07:29, 5 July 2022 (UTC)


 * Hello! As I can see, the translation was done by Google Translate. It's not good. I've used DeepL and this message is very different in English. Why do you think Vector 2022 was not originally designed to be comfortable to use as a reader? I would like to understand what made you think so.
 * こんにちは！ ご覧のとおり、翻訳はGoogle翻訳によって行われました. 良くない.  私はDeepLを使用しましたが、このメッセージは英語では大きく異なります.  なぜVector2022は、もともとリーダーとして快適に使用できるように設計されていなかったと思いますか？ どうしてそう思ったのか理解したい.  SGrabarczuk (WMF) (talk) 02:06, 12 July 2022 (UTC)
 * SGrabarczuk (WMF)-san, your great DeepL-ed message causes a deletion discussion due to copyright violation. I wish a good Foundation staff would deeply understand the copyright policy in Wikipedia and recognize that copypasting from machine translation could violate the copyright that was attributed to that translation service.
 * So, while I'm not the original poster of this section, let me answer the question:
 * > Why do you think Vector 2022 was not originally designed to be comfortable to use as a reader?
 * If you think the only problem is new Vector 2022 design itself, I must say you are missing an important point: how you all introduced the new skin. All of the changes has never been announced in jawiki before being applied (and unfortunately, after that, until today). Many of the editors, the readers, the users were surprised at the new design all of the sudden, and not a few of them regarded it as a big bug or something.
 * You may wonder, "we let you know this in advance, via a member of your community." That's true, partially. AppleRingo777-san took your messages and passed them to us per your instruction. I heard that you (or someone in Foundation) asked to post the message in WP:NEWS. How did you determine that WP:NEWS, generally where announcements only for the editors are posted, was enough to communicate this important news that obviously affected the entirety of community members including the readers? Will you also assign the responsibility on this to AppleRingo777-san, a good community member? I cannot help but want the Foundation to realize that you all destroyed our trust. --2400:4052:3420:4500:444C:45BF:13AC:59E2 14:40, 14 July 2022 (UTC)

Listed coordinates overlapping with header weirdly
for an example of this, see wp's london article (screenshot) LarstonMarston (talk) 20:00, 5 July 2022 (UTC)


 * Thank you @LarstonMarston. In this case, we need to fix the bug together with the communities - some code should be changed by editors on each wiki with this bug separately. We can help (and we're working on it). SGrabarczuk (WMF) (talk) 16:11, 6 July 2022 (UTC)
 * thanks, good to hear LarstonMarston (talk) 20:06, 6 July 2022 (UTC)

Default to Collapsed Menu Exposed TOC
I was trying to figure out why I didn't like the new TOC, and then it hit me that the main reason was that it is hidden by the side menu when you first visit a page (I very rarely login to Wikipedia, and I'm thinking that's the norm for most visitors). Then I was thinking that I almost never use the main navigation links, they just aren't part of my normal use case of visiting Wikipedia (it is to learn a specific thing that I don't currently know enough about). I was going to post to make it possible to hide the main nav, but then realized that you already built it, but the default is for it to show. My hypothesis is that the bulk of users don't look or click on any of the menu items, and that the menu should be hidden by default and the TOC exposed above the fold. 195.134.163.110 10:34, 6 July 2022 (UTC)


 * Yes, TOC should be exposed above the article not on the right. In fact in desktop view if I click PC version it does not open stuff on the left. 2A00:1370:8184:2478:A928:87EF:D073:FEEA 16:22, 6 July 2022 (UTC)
 * Thank you for your feedback! We are planning on implementing this change within the next couple of weeks. Progress can be tracked in the phabricator ticket linked above.   OVasileva (WMF) (talk) 10:04, 11 July 2022 (UTC)


 * I would like you to give logged-in users the right to choose that as well. If you knew about these plans, don't you think that was a little premature to set Vector (2022) as the default in JAWP ? If you make changes right after you start it in JAWP, Japanese users will be confused. --呉野 (talk) 13:21, 14 July 2022 (UTC)

Replace the "new section" tab text with "+" gadget not working.
On the English Wikipedia upon switching to Modern Vector the aforementioned gadget ceases to function as intended.

Nathanielcwm (talk) 13:14, 6 July 2022 (UTC)


 * Looks like the gadget is setup to only work on Vector and Monobook. I have updated it to also apply to Vector 2022 skin (https://en.wikipedia.org/w/index.php?title=MediaWiki%3AGadget-addsection-plus.js&type=revision&diff=1096783301&oldid=1047498910) Jdlrobson (talk) 15:59, 6 July 2022 (UTC)

July
@SGrabarczuk (WMF): Does Vector 2022 will be deployed (as default) at all Wikimedia wikis until the end of July, as it is written here? I am asking this because I see that there is still some work to do and the deadline written there changed several times. -- NGC 54  ( talk |  contribs ) 21:56, 6 July 2022 (UTC)


 * Hello @NGC 54, thanks for this question. This information is already outdated. It will not be deployed in July. We hope to send an update to the village pumps next week. We're working on the announcement right now. SGrabarczuk (WMF) (talk) 16:01, 7 July 2022 (UTC)

Language switching
Hi, I really appreciate the suggestion of translations within the language button, thank you! 37.103.14.65 09:06, 7 July 2022 (UTC)


 * Thanks! Appreciation also goes to the Wikimedia Language engineering team, because they have made this particular change. We have "only" provided the language button :) SGrabarczuk (WMF) (talk) 02:01, 12 July 2022 (UTC)

Vector (2022)のウィキペディア日本語版への導入について About the introduction of Vector (2022) to the Japanese version of Wikipedia
「ja:Wikipedia:井戸端/subj/デスクトップ版外装（スキン）改善バージョンの実装について」での案内によると7月14日までこのページでコメントを受け付けるとのことなので意見を書く. --匿竜類 (talk) 02:25, 8 July 2022 (UTC)
 * 開発者は開発すること自体に喜びを感じるべきであり、日本語版で行ったように強引に導入して「見えるところ」に成果が表れることに喜びを感じるべきでない.
 * 開発者は裏方として、開発に専念するべきであり、それを使うかどうかは「利用者」の判断にゆだねるべきである.
 * スキンはインフラストラクチャーである. 技術者が陥りがちな間違いだが「新しければよい」というものではない.
 * 現在のVector (2022)は完成品とは言えずベータテストの段階でしかない. この段階で全面導入を進めようとするのは技術者の姿勢として適切でない. ベータテストは希望者を募って行うべきである.
 * Vector (2022)をデフォルトのスキンとすることについて、本当に開発者チームに権限が与えられているのか. 証拠があるなら、リンクをつけて示してほしい.
 * 今回の経緯を見ると「読者」に対する観点が脱落している. 「読者」のいない記事に何の意味があるのだろうか.
 * ja: Wikipedia: Idobata / subj / Desktop version According to the guidance on implementing the improved exterior (skin) version, comments will be accepted on this page until July 14, so I will write my opinion.


 * Developers should be delighted with the development itself, and should not be delighted with the "visible" results of the forcible introduction as was done in the Japanese version.
 * Developers should concentrate on development behind the scenes and leave it to the "user" to decide whether or not to use it.
 * Skins are infrastructure. It's a mistake that engineers tend to make, but it's not "just new."
 * The current Vector (2022) is not a finished product, it is only in the beta test stage. It is not appropriate as an engineer's attitude to proceed with full-scale introduction at this stage. Beta testing should be done by recruiting applicants.
 * Is the developer team really empowered to make Vector (2022) the default skin? If you have proof, please link to it.
 * Looking at the history of this time, the viewpoint for "readers" is missing. What does an article without a "reader" mean? 匿竜類 (talk) 02:25, 8 July 2022 (UTC)
 * Hi @匿竜類 - Thank you for your feedback and for the bug reports below. We are currently in the process of taking the Vector (2022) skin out of beta testing/pilot mode and into the stage where we scale the skin, with the hopes of making it the default on all the wikis.  Over the course of the next month, we will be hosting conversations with the largest Wikipedias and getting their feedback on the skin, similar to our conversations with Japanese Wikipedia right now.  Even when default, logged-in users will still be able to chose whether they want to use the skin or not.  If they decide not to use it, they can turn it off at any moment in their user preferences.
 * In terms of readers, for every change we have made when building the skin, we have tested both quantitatively and qualitatively with readers and well as editors. To access more detail on the research and testing we have done, please go to the Features page and select the feature you are interested in learning about.  From there, you can read the sections named Quantitative research or Qualitative research to see the testing we have done. In addition, we have also done more open-ended testing with readers to identify the issues with the skin starting in 2020 until now. Please see the  Hureo User Research Report with Readers and Editors, the Wikimania Stockholm research report, the Wikimedia Desktop Usage and Behavior Data Analysis, or the Sticky Header and Table of Contents User Testing reports for some examples of the studies we have done with readers (which have translations in Japanese), what we have learned, and how we used those learnings to create the new skin. OVasileva (WMF) (talk) 10:00, 11 July 2022 (UTC)

Vector (2022)の不具合の報告 Report a bug in Vector (2022)
日本語版でVector (2022)を使うと、左側に「このWikipediaでは言語間リンクがページの先頭にある記事タイトルの向かい側に設置されています. ページの先頭をご覧ください. 」と表示されるのだが、実際には「記事タイトル」は「ページの先頭」ではなくこのメッセージの下に表示される. 以前は、このようなことがなかったように思うので一時的なものかもしれないが、症状が出ていることを確認してほしい. When I use Vector (2022) in the Japanese version, it says "In this Wikipedia, the interlingual link is located opposite the article title at the top of the page. Please see the top of the page." However, in reality, the "article title" is displayed below this message instead of "at the top of the page". I don't think this happened before, so it may be temporary, but please make sure that you have symptoms.--匿竜類 (talk) 02:42, 8 July 2022 (UTC)


 * 上記不具合を報告してから、1日経過していますが、応答がありません. ja:Wikipedia:表示改善依頼によると、どうやらこの種の不具合はファブリケータで処理することになっているようですが、そちらの方への連絡はしていただけたのでしょうか. とりあえず担当者の応答を求めます. One day has passed since I reported the above problem, but there is no response. ja: Wikipedia: Display improvement request #Vector (2022) In the skin, the badge and the map tag are displayed overlapping. According to #, it seems that this kind of defect is to be handled by the fabricator. Could you contact that person? For the time being, ask for the response of the person in charge.--匿竜類 (talk) 03:05, 9 July 2022 (UTC)
 * Hello! The coordinates issue is known but the language one wasn't. Thank you for bringing it to our attention.
 * I will reply with more details next week. Have a great weekend and thank you for the bug reports. Jdlrobson (talk) 18:27, 9 July 2022 (UTC)
 * These are tracked in T303267 and T281974. Thanks for the report! Jdlrobson (talk) 16:39, 11 July 2022 (UTC)

Merge [ca-view] and [ca-nstab-main] in the article toolbar
Currently, in the article toolbar, we have two links (Read and Article) that lead to the same location. One of them is located in the left and the other one is located in the right navigation. This can be confusing to readers, and also adds unnecessary weight to the toolbar. Current look.

It would be good if we could merge these two tabs into one. Ideally, the best solution, in my opinion, would be to merge the right and left navigation and center the items, like this. Please tell me what you think about this. Thank you! — Aca (talk) 11:18, 9 July 2022 (UTC)


 * . Now, the tabs are clear. You have 2 pages: the article and the talk page. You can select 1 action at a time for each of them: reading, visual editing, source editing, and viewing the history. Form the proposed design, you can understand that the tabs led to different types of pages. The watch is something not related to the article? And if now you are on article tabs, if you would press on the editing source tab, you would arrive on a page not related to the article (this is a possible confusion)? And so on. "This can be confusing to readers," - how so? Are there any data? And if there are, are there any data that the proposed design is better? P.S. I also dislike the proposed design, due to visual reasons. -- NGC 54  ( talk |  contribs ) 19:00, 9 July 2022 (UTC)

Big blank space when on a big zoom
Unlike the old layout that adjust depending of the size of zoom, the new format seems to follow a single size that, when zoomed in, creates a big blank space like if the page was still loading

It needs be fixed so the wiki pages can be better for people that have vison issues

- User:Meganinja202 | ¿ 10:17:00 11 July 2022 (UTC) Meganinja202 (talk) 10:17, 11 July 2022 (UTC)


 * User:Meganinja202 are you taking about Reading/Web/Desktop_Improvements/Features/Limiting_content_width or reporting a bug? If the latter, what browser and device are you using? Jdlrobson (talk) 16:34, 11 July 2022 (UTC)
 * i think should be a bug since its a thing that happens from top to bottom of the page and not from the sides, i am use Chromium Based MS Edge Meganinja202 (talk) 17:02, 11 July 2022 (UTC)

Language box recommendation
A minor suggestion: why not insert the language box on the title header so I don't have to go all up to the top of the page to change language versions. So yeah, thanks! PeaceSeekers (talk) 11:00, 11 July 2022 (UTC)


 * ya, they should had kept the language bar on the side of page instead of the top, leaving the language option on top only on mobile/touch machines Meganinja202 (talk) 17:03, 11 July 2022 (UTC)
 * @PeaceSeekers - do you use the site while logged-in? If so, you can access the language switching button from the persistent ("sticky") header at the top of the page while you're scrolling. We are also in discussion of bringing this functionality to all logged-in users as well.   OVasileva (WMF) (talk) 08:15, 12 July 2022 (UTC)
 * I did log in, but I can't see it though ... what I have is only, from the left: the search button, article title, discussion page, edit history, watchlist and my profile stuff (for lack of better words). So that's that. PeaceSeekers (talk) 08:43, 12 July 2022 (UTC)

What I still would love to see different solutions to
I'm very much looking forward to not having the text fill an entire wide screen. This will make Wikipedia far easier to read on big screens. Thanks! A few things that still don't work for me:

Table of contents

If I haven't collapsed the left menu, the ToC is not visible when I start reading the article. This makes it more difficult to get an overview.

It's also generally more difficult to get an overview of the article content, as I need to go to the ToC in the sidebar and scroll down to see everything on big pages (like a Village Pump). This both makes it more difficult for me to conceptualize what's on the page – as I've tested this, I've realised I find it challenging to get a grasp of a page if I can't see the various topics at the same time – and adds more work, as I have to move the mouse pointer to the ToC to be able to scroll. I would have much preferred if it used more of the space available to get around this.

My contributions

My own user contributions is something I use all the time – it's my way of getting back to what I was doing before. Making it less accessible in the top menu is wrench thrown into my workflow.

Language links

This is my main issue. I use other languages all the time. As a reader, I glance at them to conceptualise the topic – which languages have written about this subject? This hints at things that aren't available in the content itself. As an editor, I check out other languages to see what sources they have and so on. Having to click to even see if there are languages I can read is an extra step that both requires more work, but also makes it less inviting, as the opportunity doesn't stare me in the face. This is so central to my workflow that it might in itself be reason to keep using Vector 2010, but that's certainly not my preferred solution. Julle (talk) 10:13, 12 July 2022 (UTC)

feedback
asbra med maxbredd! coolt att wikipedia tar steget in i 2010-talet och blir läsbart på stor skärm.

språklänkarna blir mycket sämre. man borde kunna se språken direkt och klicka på dem, det är en sak man använder hela tiden.

jag förstår inte varför ni har bytt ut texten i användarmenyn mot symboler? det var tydligare med text. nu måste man gissa vad de betyder och många kommer aldrig lista ut det.

man borde inte behöva skrolla INNE I innehållsförteckningen för att se hela. sjukt störande att behöva gå till den och skrolla I DEN för att se vad som finns på sidan. 81.92.27.129 18:12, 12 July 2022 (UTC)


 * Thanks for the feedback!
 * (google translation)
 * max width: cool that wikipedia takes the step into the 2010s and becomes readable on the big screen.
 * language links: you should be able to see the languages ​​directly and click on them, it is one thing you use all the time.
 * Icons: I do not understand why you have replaced the text in the user menu with symbols? it was clearer with text. now you have to guess what they mean and many will never figure it out.
 * Table of contents: you should not have to scroll INSIDE the table of contents to see the whole thing. Very annoying to have to go to it and scroll IN IT to see what's on the page. Jdlrobson (talk) 19:00, 12 July 2022 (UTC)
 * ("Sjukt störande", which the machine translation rendered as "ill disturbing", means "very annoying".) Julle (talk) 00:15, 13 July 2022 (UTC)

More TOC concerns
On pages with long headings (f.i. Closure_requests), the new TOC is highly impractical. The headings are difficult to parse, sometimes cutting words in two. A lot of scrolling is also required to get an overview of what discussions to close. Will it be possible to go back to the old TOC on a per-page base? I can imagine a lot of non-article pages will have similar problems (including this one).

Less importantly, I noticed that the default is having only the top heading displayed. In some pages / articles there are very few top-level headings, and this would always require the reader to uncollapse. Can this be made more dynamic? Femke (talk) 18:09, 14 July 2022 (UTC)


 * Would it be possible (probably only on bigger screens) to use the empty white space on the right for tools (for logged-in editors), so that the TOC is less cramped? Solves two problems in one. Femke (talk) 17:00, 18 July 2022 (UTC)

incorrect translation Vector 2022（jpwiki）
The information text on where to switch languages is partially translated incorrectly. I think, "このWikipediaでは言語間リンクがページの先頭にある記事タイトルの向かい側に設置されています. " is a slightly mistaken translation. This may mean that the language switch is outside the display.

You probably meant to write that, "他言語版へのリンクは、ページ先頭の記事タイトルの右側にあります. ". But I would rather you don't adopt this with no check. 呉野 (talk) 10:01, 15 July 2022 (UTC)

'Talk' and 'Contributions' buttons shouldn't be hidden in the navigation bar's drop down menu.
We shouldn't have to click twice to get to our Talk and Contribution pages from the navigation bar. I mean, there's already a bunch of wasted white space to right of the search box and to the the left of our Userpage button for those two icons to be added in the nav bar without any problems. Some1 (talk) 02:57, 17 July 2022 (UTC)

Simple English sidebar
I notice in Simple English with the 2022 Vector, the menus on the left side of the page are to the left of the page text as they should be, but they are far above rather than beside the text. Jim.henderson (talk) 05:47, 17 July 2022 (UTC)

The new sidebar TOC is confusive, not intuitive, unusable
I strongly oppose the new sidebar TOC. It is extremely confusing, not intuitive, and unusable. The removal of the numbering for paragraphs and their transformation into collapsible lists, will make the articles and discussions unreadable, as their structure will be completely unclear.

The TOC at the top of the article right below the lead text was perfect for giving a clear impression of the article's structure and for exploring its contents.

I think that keeping both the old and the new TOC (if the latter is really necessary) would be a good solution. The new TOC proves useful only in the bottom sections of very long articles. 2001:B07:A2A:1884:D5D:3606:C70C:5366 14:03, 17 July 2022 (UTC)
 * Second that. Another point of note is that the narrow sidebar is a poor match for long section titles. Even in English wikipedia, some headings must be split in two narrow lines, or three. Other languages, that are naturally more verboise than English, are even more affected. Retired electrician (talk) 08:16, 29 July 2022 (UTC)

This gives me depression
By merely see this happen week-by-week, I can see this sacred project gradually being destroyed. I wish I could stop this. – Ilovemydoodle2 (talk) 07:35, 18 July 2022 (UTC)

wrong name for a language
someone is having a laugh, or got really confused about translation. In the main page https://www.wikipedia.org/, Français now appears as anglais, both in the top 'wheel' and in the 'Read Wikipedia in your language' drop-down. This is very wrong. What other languages have been disappeared in this way ? a bit of QA would go a long way :-) 92.16.98.145 16:23, 19 July 2022 (UTC)


 * Thanks for letting us know! This looks like a mistake/error on translatewiki.net. We'll try to fix that immediately. SGrabarczuk (WMF) (talk) 18:28, 19 July 2022 (UTC)
 * FYI this wasn't related to the project.
 * See related Reddit thread for details on what happened here if you are curious: https://www.reddit.com/r/wikipedia/comments/w2iidz/why_anglais_did_someone_sabotage_it/ Jdlrobson (talk) 20:03, 20 July 2022 (UTC)

coordinates being weird (again)
there was an issue a little while ago where location coordinates in an article would overlap with the header. that's fixed now, but some icons are still uncomfortably close to them, like the FA star; for an example of this, see the english wiki's India article (screenshot) 2600:1700:7AA1:2400:9CA1:1220:42FD:1F12 20:17, 20 July 2022 (UTC)

General concerns!
Well I was part of the process for quite some time now. And up until the move of the TOC from inside the content to the sidebar it was okay with me. I had some minor things, I thought I will get used to: the white space (anyone wanting that, can narrow their window), some inconsistencies (compare ), the language switcher, which I fear will leave the impression of reading the same thing in different languages (compare Talk:Reading/Web/Desktop_Improvements/Archive3, as a side-note: nothing happened here, at least nothing I recognized).

But today I got this message: Topic:Wsfx4tbwzkgamaek asking for a translation for Reading/Web/Desktop_Improvements/Updates/2022-07_for_the_largest_wikis. Let me cite:


 * "...before discussing the change itself"
 * "...that allows for a way to identify the needs of the community from the new skin."
 * "We would love to see the Vector 2022 skin [...] become the new default across all wikis..."
 * "We will be ready to begin making the change at the end of August (and not in July, as previously announced), when the visual refinements and other deployment blockers are ready."
 * "The goal for that discussion will be to identify breaking issues or opportunities for improvement for the new skin. It will be important for us to reduce the risk of bugs or imperfections that would be particularly troublesome on [insert your language] Wikipedia"

All that reads like: Well, we're just talking, let's see, what needs to be done, that everyone is happy. There are some things that need to be done anyways.

Now let's read those two cites:
 * "...difficult discussions about the launch as the default" (compare Topic:Wsfx4tbwzkgamaek)
 * "...until our improvements are default on all wikis in July 2022." (compare Reading/Web/Desktop_Improvements

So isn't this not just a request for bug reports instead of a "discussion"? Is this not more of a fear of "Flak" instead of "needs of the community"? Isn't it happening anyways, instead of you "loving to see it"? What about all the other projects, wikibooks for example ("[insert your language] Wikipedia")? I understand, you do the work, you decide. But:


 * Is it wise to "discuss" while there are still tasks to be done and decisions to be made? (compare Reading/Web/Desktop_Improvements/Features/Visual_Refinements, which by the way doesn't even seem finished, and for example )
 * Is the Date of the end of August (6 weeks) really feasible? Who will translate all the feedback that will come in german?
 * Is it good to leave the impression, that communities will have a choice (compare )?

Some suggestions, if I may:
 * 1) Why not try to slow the process down? Why the haste? One could remove the deadlines and refine everything. Then ask the communities for bug reports.
 * 2) Why not try some marketing "tricks"? I think the discussion about the white space clearly shows that desktop improvements are highly subjective. Why not use for example skin changes? Another Option could be deploying Vector 2022 only for not logged in users and hence prolong/smooth the transition-process creating time for bug reports and discussions. Most of anonymous usage would probably not care for the change, as long as the content is there. On another plus-side it will create "data" on how the menu-usage changes and community-links are perceived. It will probably even create data on how many logged in users switch to the new layout deliberately and or switch back hence providing "hard" success-data.
 * 3) Would it be that bad to really leave the community a choice?
 * 4) If you are relying on volunteers, grant them a little more slack. Bug reports from the community need time: Bugs need to be recognized as bugs, they need to be reported, triaged and handled. Is this possible in 6 weeks? Volunteers might have another life, a job, kids, a week might be pretty short notice. Phabricator-use is not that trivial.
 * 5) Let's talk or try, if the new design might eventually be a problem for recruiting new volunteers. Did anyone think about a possible impact of hiding community-links in collapsed menus? Nobody seems to talk about community-pages or discussion-pages or even other project-scopes. Is the new menu-structure as fitting for these as for wikipedia-articles?

I'm deeply saddened. The new TOC will make my life within wikimedia really hard and I commented about that early on (compare here, bullet 7). I think all the TOC-comments on this page (see above) should raise at least some concern. And last but not least, I'm deeply troubled, that the new language-links will do more harm, than good.

So, ping @OVasileva (WMF) and @SGrabarczuk (WMF), my sincere apology, I don't mean to be rude or mean and I appreciate your work and the work of your colleagues. But I don't want to volunteer for the translation-request, because all of the above mentioned problems.

Regards HirnSpuk (talk) 22:25, 20 July 2022 (UTC)


 * Hello @HirnSpuk. Thank you for your outstanding involvement, and appreciation for our work. I'm glad to see that. Also, thank you for your sincere, thoughtful, and thorough comment with all the links and quotes. I think I understand what your approach is, I'm happy that you're saying this.
 * Before I answer the questions, I'll admit/confirm that:
 * The ToC work hasn't been finished yet. So haven't the visual refinements. There's a list of issues labelled as "deployment blockers", by which we mean issues we need to solve before making it the default everywhere. I hope this will make you less sad!
 * Bug reports do need time. Phabricator is not that trivial.
 * While indeed focusing on the most typical use cases, like interacting with articles.
 * In some discussions, it has been confusing what exactly is for the individual communities to choose between.
 * Regarding the questions, my answers to the easiest part:
 * We've been working since 2019, most work is behind us and we're headed towards the end. Now, we need to make sure what else the largest communities may need.
 * What about all the other projects - the message I asked if you could translate is dedicated to the largest communities of the top language versions of Wikipedia.
 * This is why in that message, we're initiating a pre-discussion about culture of collaboration. After that, we'll ask for bug reports and other technical requests.
 * We use the name Desktop Improvements because the point is to make changes that are actual measured improvements. Only some of the visual refinements are really subjective. But regarding the feature changes, the idea for each of these is that it should be an improvement compared to Legacy Vector.
 * We're part of Core Experiences and work closely with the teams focusing on newbies and more experienced editors. It's our plan to make entry points for new volunteers prominent, in collaboration with Growth. We hope that Desktop Improvements will be an introduction to even more sophisticated changes addressing very specific use cases.
 * OK, enough now for one comment. Let's keep talking, though. SGrabarczuk (WMF) (talk) 01:30, 21 July 2022 (UTC)


 * @SGrabarczuk (WMF), because you said "let's keep talking", let me react to your latter 5 points.
 * I do not want to diminish in any way the work you (plural) have done since 2019 and I think the plan is good. But I'm convinced, that the timing is not right. "The end of August" I find far to soon if you "need to make sure what else the largest communities may need."
 * I wasn't able to find the "we talk to the «big guys» first"-idea anywhere. The only thing I find is "We would like our improvements to be default on all wikis in August/September 2022." There will probably not be time to talk to the «small guys». And in addition, the text to translate suggest, that there is a choice, and you'd like to "talk". My impression is you want to ask: how can we best ask for bug reports. That might (and probably will) work, but I don't want to be part of exactly this approach.
 * same as first and second.
 * How is the improvement measured? Is there any "hard data" anywhere? Everything needs more clicks hence more time. It "looks" a little better and modern, which I also find necessary and good. But what is actually "improved"?
 * I need more scrolling for the TOC,
 * I will need more work (and creative ideas btw) for rework of community-pages that rely on the "old" version of the TOC at the moment, and even worse, I need to check the visual appearance and usability of pages in even more configurations (to mobile and desktop and VE and source, now I need to add different skins),
 * I need more clicks for almost anything (if menus are hidden, but this is nearly imperative, to get at least some use out of the new ToC),
 * I'm deeply troubled about the "impression" some changes might make (which hence wouldn't be an improvement either and which is by default not measurable)...
 * What about the visually impaired? Is it an improvement for them too, any hard data?
 * Please, feel free to elaborate. I know it would be baloney to change the name in the last 6 weeks of the work. My point is not to do that, but to take a step back, review what's done so far, and if the decision will be made to prolong the process a really long time, then maybe one might think about a change, and if it's only to get less of the "if you do this I'll be done with wiki..."-criticism that's just consuming time for everyone.
 * I'm not addressing technical issues. It's the possible "hiding" of prominent community-links in the sidebar by using elaborate restructuring and collapsing mechanisms. On that the single communities won't have influence as far as I see it at the moment.
 * PS: I appreciate trying to cheer me up ("make you less sad"), but my sadness stems from the uncertainty how this will all work out. In the end the prototype is only a prototype. And how much work in the community must be done afterwards to facilitate the "improvements" is also not clear. The main point being, that I struggle with checking and cross-checking functionalities in different systems. It was okay until the move of the ToC. But as long as there is still work to be done, I can't even think about workarounds for not having the ToC where and how I was used to it.
 * Regards HirnSpuk (talk) 07:34, 21 July 2022 (UTC)
 * Hey @HirnSpuk, thank you for your continued feedback. It's been super helpful. We've rewritten our message to German-language Wikipedia based on your thoughts and the learnings we've gotten through similar conversations on other wikis. We're going to post our next draft for translation this week - let us know what you think of it! We're open to suggestions. Your continued thoughts are much appreciated!
 * In terms of your individual questions:
 * The timing is not right
 * We really do believe that our changes are improvements already! We're eager to bring them to readers and editors. As you have pointed out, we've been building these for three years. We've received feedback from German-language Wikipedians, and many other communities. As you also know, we've performed prototype testing with editors across 30+ languages, and different types of quantitative testing on each feature. Many significant requests have already been discussed.
 * The main reason we want to have this conversation now (while we're putting the finishing touches, like the visual refinements and changes to the table of contents) is that we'd like to see if any of the feedback might change what those finishing touches are. We'd also feel more confident with our plan once we know what the additional work we need to do is, if any.
 * The process we're envisioning is to collect bugs and requests, and triage these into three categories: (1) the ones that must be done before the deployment, (2) the ones that can wait until after the deployment, and (3) the ones that we don't think are a priority. Our goal for the conversation with the communities is to establish what lies in each bucket such that the communities are comfortable with changing the default.
 * We understand if a conversation might take longer on a given community, and do not plan on cutting any discussion short just to reach a deadline. We made a mistake with Japanese Wikipedia and made the change prior to acknowledging a common process. We'd like to avoid that mistake with the other wikis, hence the lengthier discussion with German-language Wikipedia.
 * The "we talk to the «big guys» first"-idea
 * We try to take the approach of equity. We have conversations across the top 25 Wikipedias by size. We've attended a Wikisource Triage meeting and two SWAN meetings. The set of pilot wikis is diverse. We inform the big and small communities about our office hours using different channels, incl. MassMessages, Tech News, Discord, Telegram, Facebook. We're going to have the interpretation support in the top UN languages.
 * How is the improvement measured?
 * Thank you for pointing this out. This very crucial piece was missing. We'll be adding a summary of our findings to our future messages.
 * You'll find the short answer on the English Wikipedia Village Pump page, quite paradoxically brought to everyone's attention using the "hidden" template. For details on any individual feature, go to the “features” section of our documentation, select the feature you are interested in, and review the qualitative and quantitative sections.
 * It's the possible "hiding" of prominent community-links in the sidebar by using elaborate restructuring and collapsing mechanisms. On that the single communities won't have influence as far as I see it at the moment.
 * This is a great question. So far, our interviews with users have shown that newcomers are NOT more likely to begin contributing based on the number (or even presence) of community links. In fact, having so many options at hand made them feel unwelcomed to the interface as they didn't instinctively know where the links would lead, and thus, felt intimidated or lost.
 * We think a better method is to have fewer links that are clearer to understand and pave more intuitive ways. These links are, among others, edit or history. We are working with the Growth and Editing teams to identify how we can increase the understanding of these links for readers and newcomers - both so they will know where the content they are reading is coming from, but also as a means of introducing them to contribution. See also: Core Experiences.
 * What about the visually impaired? Is it an improvement for them too, any hard data?
 * We've been doing accessibility testings with the American Foundation for the Blind. You'll find more information in this task: T310033. Generally though, part of this work goes beyond Desktop Improvements, and is done by our designers who build basic user interface elements for all the teams.
 * Hey, on a side note, have you ever attended our office hours? I (Szymon) don't recall this. You'd have heard answers to some similar questions if you had joined us earlier. Anyway, feel invited.
 * OVasileva (WMF), SGrabarczuk (WMF) (talk) 02:44, 29 July 2022 (UTC)

Sorry but user expereince is kind of awful
Okay. I've given "Vector 2022" a shot for a while and it is just confusing and difficult to use. Too much animation-style issues. Too much whitespace. Difficult discovery of functions. Difficult to obtain a feeling of confidence in mastery. If I would have been keeping a log, I'd have dozens of gripes by now. I don't wish to waste time enumerating specific things because it's besides the point because the entire experience is bad. I can't hack it anymore. I thought I'd get used to it but I'm going back to Vector 2010. Keep things simple. Keep it static. I know many people but a lot of work into this and it was a valid attempt but it just didn't suceed in improving over Vector 2010. Jason Quinn (talk) 02:24, 26 July 2022 (UTC)

External link icon
The external link icon currently deployed on mediawiki.org looks horrible. What happened? The icon shown at T261391 in the "After" screenshot looks much better. -- NGC 54  ( talk |  contribs ) 19:55, 26 July 2022 (UTC)


 * @NGC 54, what's the difference you're referring to? Could you maybe share a screenshot? SGrabarczuk (WMF) (talk) 23:36, 26 July 2022 (UTC)
 * @SGrabarczuk (WMF): Here.
 * Vector2022 Broken External Link Icon.png -- NGC 54  ( talk |  contribs ) 10:48, 27 July 2022 (UTC)
 * I saw that the issue was already reported. Compare this with this. Also, for me it looks like the arrow is misshaped. -- NGC 54  ( talk |  contribs ) 10:53, 27 July 2022 (UTC)
 * Hi @NGC 54 - thanks for your report. The icon is indeed broken as of right now.  We're looking into this right now and hope to have a fix later this week or early next week.   OVasileva (WMF) (talk) 12:05, 28 July 2022 (UTC)

Sticky header causes TOC to instantly offset on appearing
When scrolling down a page, at the moment the sticky header shows up (smoothly), the TOC offset is incremented to display below the header. However, the TOC offset change is instant, unlike the header. It's just a small visual thing, but I think making the TOC offset to follow the smooth header apparition would make pages look more reactive. Regards, Epok (talk) 18:54, 29 July 2022 (UTC)

Sticky sidebar overlaps footer
I wonder if anyone have noticed it: when you scroll down until the end of the page (from a desktop) the sticky sidebar overlaps the footer. Because of this, it's impossible to read part of its content and it looks pretty weird. I don't know much about how MediaWiki works, but maybe applying z-index and background-color (or something similar) to the footer could be a possible solution?

Cheers, Anidae (talk) 22:18, 29 July 2022 (UTC)
 * Hello @Anidae. Thanks for writing here. Yes, we've noticed the bug and we'll fix it. SGrabarczuk (WMF) (talk) 11:49, 1 August 2022 (UTC)

CSS gadget to truly disable max-width limit (on jawiki)
Hi, developers. I am aokomoriuta, a.k.a. jawiki sysop&IFA, and was the Phase III UX Ambassador for the (legacy) vector skin switching.

In this thread, I'd like to notify you (developers) about the gadget NewVector-MaxWidth.css, which is provided on Japanese Wikipedia to solve the max-width problem on Vector2022 and problems on the gadget linked from your FAQ page.



I understand why you think the limitation is reasonable. I won't make a counterargument to limit max-width as the default settings.

However, the limitation is NOT THE BEST FOR ALL USERS, but only most. Some users (including me) want to read Wikipedia and other articles as wide as possible (the browser's window-width).

I know you linked the gadget for such users (en:User:Jdlrobson/vector-max-width-toggle.js) from the FAQ page.

I tried it, but it's not good for me. There are three problems;


 * I need to click the button to switch the width on each page.
 * I can feel a little latency to see the switched page because JavaScript might take some instructions to overwrite the width settings, especially on my light laptop computer.
 * The width is not maximized. It makes the width only about two times. As I wrote above, it is not enough.

To solve the above problems, I have provided a user custom css (ja:プロジェクト:ウィキ技術部/スクリプト開発/trunk/newvector-maxwidth.css) to truly maximized the width on Japanese Wikipedia.

This method is significantly lighter than the gadget you provided, and easy to maintain because it needs only to specify the element's class/id which you limit the max-width. I will continue to maintain and provide Japanese Wikipedia users as long as I don't find an alternative way.

You can link the CSS from your (FAQ) pages, or take over its development and maintenance to provide all Wikimedia sites. I also welcome feedback/request/comments from all developers and users. Please reply in this thread.

I hope this thread and your developments improve user experience successfully.

日本語版の利用者の方へ(For Japanese users)：ガジェットに関する意見・要望・コメントなどはja:Wikipedia‐ノート:ベクター (2022年版)/横幅制限の撤廃でも受け付けていて、日本語ができる人はそちらに書いてもらったほうが応答や解決が早いと思います. aokomoriuta (talk) 06:58, 31 July 2022 (UTC)

Design decision against the Wikimedia Movement strategy recommendations
Hello! The Desktop Improvements (sic) project has decided, against the Wikimedia Movement recommendations, to hide by default the links to sister projects to non logged users. The Improve User Experience recommendation textually says:


 * Tools to connect cross-project and cross-language functionalities to provide an enhanced experience of the knowledge contained in the Wikimedia ecosystem for a particular interest, informational need, or inquiry. (bold text is mine).

We can have different views on aesthetics, but hiding the cross-project links instead of making them more prominent is against the recommendations. I have tried to discuss this in Phabricator, but there doesn't seem to be any way to discuss seriously this error. Thanks. Theklan (talk) 20:27, 1 August 2022 (UTC)


 * Theklan, thank you for your concern and for keeping us on our toes. To clarify: the idea behind the goal that you've quoted is is to build systems and tools (such as structured data) that allow us to incorporate content from sister projects within Wikipedia. As we know from data collection simply linking to sister projects does not work effectively. So I respectfully disagree that we're are going "against the Wikimedia Movement recommendations".
 * Secondly, as we've discussed in the past: with each improvement comes a tradeoff, and sometimes when our principles/goals conflict with one another we are forced to make difficult decisions. So even if we had a movement goal to provide links to sister projects (which we do not), it still might be okay to collapse those links in some cases. We cannot offer people every link at all times — we know from research that this decreases the quality of the overall reading experience. So yes, the links in the sidebar are more difficult to access now. We are already aware of this. But the overall improvement to the reading experience makes this tradeoff worth it. This is the conclusion we have arrived at through data collection and testing. These decisions are not easy to make, and we know that certain people will be upset by them. I am sorry if you disagree with the conclusion we have come to.
 * Thankfully the Structured data team are actively working on various experiments that bring content from sister projects directly into Wikipedia. You can read more about that project here: https://phabricator.wikimedia.org/T306341. AHollender (WMF) (talk) 22:31, 1 August 2022 (UTC)
 * "Bring content from sister projects directly into Wikipedia" doesn't seem like a recommendation, because we can also bring content from Wikiquotes to Wikisource, without using Wikipedia. So, sorry, but no. This recommendation is clear: disconnecting cross-project links goes against the recommendation. Theklan (talk) 07:58, 2 August 2022 (UTC)
 * @Theklan you can read more about how content from sister projects is being incorporated into Wikipedia here: Structured Data Across Wikimedia/Search Improvements AHollender (WMF) (talk) 16:03, 2 August 2022 (UTC)
 * That's a good initative, yes. Is not related to what we are discussing here. What are the steps to make links to sister projects more prominent in the new design? Theklan (talk) 08:04, 3 August 2022 (UTC)
 * In my understanding that question was already answered above: "simply linking to sister projects does not work effectively". --AKlapper (WMF) (talk) 10:35, 3 August 2022 (UTC)
 * "Simply linking to sister projects does not work effectively" can be a good sentence. Just deleting the links is, surely, less effective than having there. If the links there are not effective, we should have a place to put them on (that was my only point in the Phabricator ticket, but as usual it gets ignored, or the discussion goes to harassment if I have a point). Is there or will there be a place to put the links, or are we going to get rid of them just because they weren't prominent? (I remember that I have been constructive in this discussion, I even presented a mock-up to make my point more clear). Theklan (talk) 17:49, 3 August 2022 (UTC)
 * @Theklan I think collecting data is a good first step, so we can better understand how the previous solution was being used. I am hesitant about adding more menus/links around the content, again because we know from the data that the links in the sidebar weren't being used much, and that they distracted from the reading experience.
 * Would it be possible to explore the usage of these sister project link templates on Basque Wikipedia? I wonder if we can also collect data for clicks to those templates. Also would it be possible to experiment with adding these links to infoboxes on some articles?
 * Screenshot_of_sister_project_links_template_on_Albert_Einstein_article.png
 * Screenshot_of_sister_project_links_template_on_Muhammad_Ali_article.png
 * AHollender (WMF) (talk) 18:56, 8 August 2022 (UTC)
 * Links to Commons are added to every infobox at Basque Wikipedia if a Category exists. All those links are at the bottom, and are included by hand. Some big wikis have it automated, and we also have it automated at Basque Wikipedia, because we use Wikidata extensively. Is not the case for 800+ wikis. We could just make things easier, and add the links to cross-wiki projects (as intended in the Movement Strategy) somewhere visible. For example, below the title. That would be a move along the Movement Strategy. Theklan (talk) 19:21, 8 August 2022 (UTC)
 * which data collection? David Wadie Fisher-Freberg (talk) 13:33, 7 August 2022 (UTC)
 * @David Wadie Fisher-Freberg my apologies — after reviewing the data I realized that those links were not included (to clarify: "wikidata" refers to all sister project links):
 * "'Donate, store and wikidata links currently excluded. Unable to track as they direct to external sites. Need instrumentation.'"
 * The report is here: https://nbviewer.org/github/wikimedia-research/Desktop-behavior-analysis-Aug-2019/blob/master/Desktop_usage_behavior_analysis.ipynb#Sidebar-links
 * So we know, high level, that people were hardly clicking most of the sidebar links (which is why I made the assumption about the sister project links). We are now discussing as a team how we can collect data about these links. I apologies again for providing incorrect information. AHollender (WMF) (talk) 17:44, 8 August 2022 (UTC)
 * thank you for your reply. I am deeply concerned with this change, and without more information I doubt that I could buy the "no one's clicking this so we should remove it" argument. Would appreciate if there is a clearer timeline and plan from your side on the planned data collection for the links. Thanks, David Wadie Fisher-Freberg (talk) 12:26, 9 August 2022 (UTC)
 * At the same time, it would be a wise move to reverse the sidebar hidding, while a solution to the cross-wiki links is found and we gather data about real usage. Theklan (talk) 11:33, 10 August 2022 (UTC)
 * @David Wadie Fisher-Freberg right, so the tricky thing is that we can't have everything on the screen at once. In order to improve the interface there are tradeoffs we have to make. What is more important: having the best reading experience possible, or having links to sister projects immediately available on the screen? What is more important: having immediate and persistent access to the table of contents, or immediate access to links to the sister projects? Collapsing the sidebar allows us to significantly improve the reading experience, and make the table of contents immediately accessible. In our opinion these features are of higher order importance. We want the site to be welcoming to everyone, and ideally be the best place on the internet for reading and learning. I think we can work together to figure out what to do about these links, but it would be helpful if you could acknowledge that the changes we've made are for good reasons. We need to think about the "forest", not just individual "trees" (or we will end up again with a cluttered, confusing interface). AHollender (WMF) (talk) 17:17, 12 August 2022 (UTC)
 * I understand the perspective which you came from. I don't agree that removing the links to sister projects would obstruct the aim to have the best reading experience possible. Our Strategic Direction explicitly stated that by 2030, "we will become a platform that serves open knowledge to the world across interfaces and communities". This decision of yours would stand in its way. I agree we can work together to figure out what to do about these links. My suggestion is to keep it where they have been for many years. David Wadie Fisher-Freberg (talk) 04:03, 13 August 2022 (UTC)
 * There's even a better suggestion: make them more prominent. Just use the tagline, that is the most visible place in all the screen. Theklan (talk) 09:55, 13 August 2022 (UTC)
 * @AHollender (WMF) Can we at least get confirmation that you will not try to sabotage local language versions that will add these links back in their common css/js files because they think they are important? Perhaps will you even make sure such local changes are easy (in line with the strategy Enable the empowerment of local communities) by providing simple configuration and documentation? Ainali (talk) 13:46, 7 August 2022 (UTC)
 * Just to clarify, @Ainali, the links won't disappear, but will be hidden if you don't click on the menu button. Istead of looking for a better and more prominent place for them, they will be hidden from general public, making our ecosystem poorer. Theklan (talk) 17:15, 7 August 2022 (UTC)
 * Yes, I understood. I meant "add back" as in make them easily available again. Ainali (talk) 17:37, 7 August 2022 (UTC)
 * @Ainali thanks for your question. As I mentioned above, each link in the interface comes with a tradeoff (often to the reading experience). If communities decide that the inclusion of these links directly on the page (i.e. not within a menu) is important to them, we will support them in figuring out a way to make this modification. AHollender (WMF) (talk) 17:48, 8 August 2022 (UTC)
 * Again, Alex. Is not that is "important to them". Is that is important for the whole movement as stated in our Movement Strategy. I was part of the team who made the recommendation, so trust me: we were talking about this. Theklan (talk) 19:23, 8 August 2022 (UTC)

As a courtesy notification, I've also inserted this to the ongoing discussion at English Wikipedia. David Wadie Fisher-Freberg (talk) 04:46, 13 August 2022 (UTC)

Survey
Does this survey will be run on English Wikipedia only? -- NGC 54  ( talk |  contribs ) 09:25, 2 August 2022 (UTC)


 * @NGC 54 - no, we will be running the survey on approximately 10 languages, depending on where we are able to get translations. We're starting with English Wikipedia while we wait for translations for other language wikis.   OVasileva (WMF) (talk) 11:15, 2 August 2022 (UTC)

Namespaces in the search menu
It seems it is possible to improve the search as follows. For example, only for registered users. Editors often have to search for templates and links to help pages in the Wikipedia namespace, and registered users can probably do this more often than they type the names of articles in the search. To do this, it is convenient to type the name of the page directly in the search field, for example: "template:page name", "wikipedia:page name". It is even more convenient to type this with aliases of the namespaces "t:name" and "wp:name". The inconvenient thing here is that you need to type the ":" character. Someone can switch the layout to English for this, where ":" is easier to type. And someone does not know about keyboard shortcuts on their language layout at all (there are even people who select and copy with the mouse and refuse to copy through ctrl+c/ctrl+v). It seems it would be convenient to have a namespace selection feature right in the drop-down list. For example, if it were possible to switch the search to these namespaces (or add these namespaces to the search output) if the namespace alias was the first "wp name" - this is implemented in browsers when you can first type "site search shortcut" in the address bar. Sunpriat 21:18, 2 August 2022 (UTC)


 * Hi @Sunpriat. First of all, thank you for all your suggestions. I've taken the liberty and separated these into different topics. I think it'll be easier to talk. I needed to create the headings, and I tried to get the ideas reflected well, but if you think the headings could be better, please edit. You're the original author here.
 * Regarding the namespaces in the search menu, I could swear I've seen something like this somewhere. I'll ask my team if we could do anything about it. Perhaps this would be a task for a separate team working just on the search... well, I'll get back to you. SGrabarczuk (WMF) (talk) 18:34, 4 August 2022 (UTC)

The header area in the new editor is not active for clicks and text selection
Sometimes when editing pages, it becomes necessary to select the page title and copy it. If you open editing in the 2017 wikitext editor (for example, a random page that you have not opened before or you do not save site data through the browser settings), then the title is gray and it cannot be selected and copied. If you open (also a random page) for editing in the Visual editor, then the title is black and it can be selected and copied. It is necessary that you can always select and copy the title. Sunpriat 21:18, 2 August 2022 (UTC)

Open in reading mode without using scrolling
It is often necessary, when a page is in editing mode, to open a duplicate page in reading mode in a new tab to view or use a wiki link or footnote. Somewhere it was announced that you saw how much less often users began to scroll back to the beginning. To open a duplicate page, you need to scroll up, then down again to the place of editing. Maybe someday you will have ideas on how to open the reading mode without scrolling. Sunpriat 21:18, 2 August 2022 (UTC)

Add a help link to the languages widget
As a registered user, I would like to see languages that are more understandable to me higher in the list, for example, English. For many users, the main question is how to make specific languages higher. About this maybe there is somewhere deep in the help. But it seems it would be more useful to somehow find out that the user can influence the list of favorite languages, or go to this help from the menu itself with a minimum of clicks. And I would also like to know how to get rid of unnecessary suggested languages, which I clicked only once. Sunpriat 21:18, 2 August 2022 (UTC)

Placeholder for the search languages widget
As an editor, I sometimes have to open wikis in languages that are mentioned in the text (for example, as a country) or used in an article (for example, as a word in a lang-x template). I understand in my own language what the language I need is called, but I do not know its original writing, which is shown in the drop-down menu. The first thing I do is spend time scrolling the list up and down in search of something similar. Yes, you can enter a name in the "search", but this is 1) not very often required 2) you need to know about it in advance or remember, or the old experience of the language list prevails without this "search". The problem is that the text "Search for a language" is too standardized and speaks poorly about the possibilities. I would like this placeholder to somehow directly and better than now tell me "how" to find (describes the actions - what should I type) a language if I know its name in my language. In my opinion, as the best example, the text in the placeholder of the field suggesting that we write a description of the edit when publishing the page "Describe what you changed" is much more informative and better suggests what needs to be done. Sunpriat 21:18, 2 August 2022 (UTC)

Languages' names in the language of the interface
For the old location of languages in the sidebar, a user script was made locally ( iwlocalnames iwhints iwcore), which registered users could enable for themselves and see the names of languages in their own language. It seems that this script was quite popular. It may be worth making a switch in the menu for everyone, even for unregistered users, which could change the language names to the interface language of this wiki (or the interface language that is selected in your settings) and back to self-names in one click. Sunpriat 21:18, 2 August 2022 (UTC)

Offer more pages in the search using the technology of translators
You said that readers prefer to look at one language and somehow "don't know" about other languages, and for this the language selector was placed at the top. If we look at enwiki, where there are 6 million articles, then this is much more than in other language wikis. When you search in yandex, an offer to read an article in enwiki through their translator often appears in its output. For example, if we search for "список портов по грузообороту", the search site will offer us this article "List of busiest ports by cargo tonnage in the following form . We have already used yandex in the Content translation extension. Perhaps for some translation directions it would be possible to suggest in our search to view the page in / through their translator. Or only show results from another language wiki by somehow translating the query (for the search engine itself, in the same way as they do, but by any translator) from the language of the current wiki. (From the point of view of spreading knowledge, this makes sense. It is unclear in what form it could be.) Sunpriat 21:18, 2 August 2022 (UTC)

Add a link to the FAQ
It may be useful to add links from the old Structured Discussions/FAQ to the Reading/Web/Desktop Improvements/Frequently asked questions, the information (by links) in it at that time looked convincing. Sunpriat 21:18, 2 August 2022 (UTC)


 * Huh, you've found an old and potentially useful page. Your idea is good. However, there's an issue about the context. The Foundation isn't doing anything about Structured Discussions. I imagine if we provided this link, it would look like we were encouraging more people to use Structured Data, or like these projects were connected. What do you think? SGrabarczuk (WMF) (talk) 18:25, 4 August 2022 (UTC)
 * I meant reusing these links "Whitespace myth", "Best practices analysis" and footnotes, not links to the Flow help Sunpriat 18:37, 4 August 2022 (UTC)
 * Oh, OK, thank you for clarification! SGrabarczuk (WMF) (talk) 20:11, 4 August 2022 (UTC)

ToC in the diff view
In revision comparison mode, ToC looks like a regular bulleted list without styles https://en.wikipedia.org/w/index.php?title=Botany&diff=1101340041&oldid=1098510198&diffmode=source Sunpriat 21:18, 2 August 2022 (UTC)
 * Thank you, we'll work on it. You can follow our activities on Phabricator. SGrabarczuk (WMF) (talk) 12:08, 4 August 2022 (UTC)
 * I think it's a wrong phabricator task. There are no images with "* 3.5" there. IKhitron (talk) 23:17, 10 August 2022 (UTC)

Feature request
Hey, I love the new Vector styles overall, but the user menu is the one area that slows me down. I tend to use my user contributions page a lot to check recent activity on articles I created or edited recently, because my watchlist is quite large. Other editors might frequently use tools collapsed in the menu like their Sandbox, but not user contributions or a watchlist.

Consequently, I'd love more flexibility when it comes to...
 * 1) how many menu items are shown in the header vs in the collapsed menu. On many monitor sizes there is a lot of wasted whitespace in between the search field and the user menu, and being able to show more items and then have it collapse dynamically as the viewport shifts is basically what the whole point of a more modern header layout is for.
 * 2) the ability to customize which menu options are in the header based on my needs, so for that for instance I could hide notifs (I get very few alerts) but show user contribs.

This kind of customization is similar to how the Slack sidebar can be reordered hierarchically by each user, but with sane defaults in place. This kind of addition would let us keep the same basic principle of a more refined set of menu items with a dropdown for the rest, but let users decide for themselves which tools they need quick access to the most.

Steven Walling (talk) 18:02, 3 August 2022 (UTC)

Sidebar overlapping
The main menu sidebar is overlapping (Vector 2022). Unusable. Grimes2 (talk) 14:20, 4 August 2022 (UTC)


 * Hello @Grimes2, thanks for writing here. Is this about the issue reported in ? SGrabarczuk (WMF) (talk) 17:56, 4 August 2022 (UTC)
 * No! https://abload.de/image.php?img=2022-08-0420_03_33-grxcjnf.png Grimes2 (talk) 18:09, 4 August 2022 (UTC)
 * I can't replicate this :/ Let's perhaps add ?safemode=1 to the URL and see if the issue still exists? SGrabarczuk (WMF) (talk) 18:24, 4 August 2022 (UTC)
 * No success. https://abload.de/image.php?img=2022-08-0420_35_52-gr10kgs.png Grimes2 (talk) 18:39, 4 August 2022 (UTC)
 * My investigation: Opera was set to font size big. Using font size normal solved the problem. Thanks. Grimes2 (talk) 18:59, 4 August 2022 (UTC)
 * This is https://phabricator.wikimedia.org/T313817 Jdlrobson (talk) 22:01, 8 August 2022 (UTC)
 * Thanks! I also solved this by reverting to the normal font size. Is it possible the new layout could take the font size into account? Ustcgcy (talk) 16:48, 12 August 2022 (UTC)

Sufficiently narrow window just shows some separator lines
I don't know when this started in the past few days, but (using Vector-2022 of course) as of now a narrow window, meaning one snapped to the right side of my 1920x1080 screen or even narrower than that, starts with the entire left-panel list of links, with their horizontal dividers spread across the window, before I even see the page title, right at the bottom of the window. Zooming the browser to 90% brings back a more normal display. This happens on every page I see; it's not dependent on images, or break markers, or the size of the TOC. I hope that's enough information without an image. I can't imagine I'm alone but didn't see any relevant subject line on this page.

Configuration: Edge 103.0.1264.77 or Chrome 103.0.5060.134, Windows 10, scaling 100%. English Wikipedia, any of several namespaces. DavidBrooks (talk) 16:42, 5 August 2022 (UTC)


 * Ditto on my Surface Pro: 2736x1824 at 175% scaling. DavidBrooks (talk) 17:59, 5 August 2022 (UTC) ETA: screenshot of this page . DavidBrooks (talk) 18:04, 5 August 2022 (UTC)


 * The master bug was closed as "Invalid" (i.e. intentional). If this ugly result of docking to the right (or left) half of an screen with HD aspect ratio is intended, then my workflow becomes untenable and I have to stop using Vector-2022. And any new user who similarly uses that Windows feature will be similarly borked. I'll try to push back. DavidBrooks (talk) 23:45, 7 August 2022 (UTC)


 * Getting off my high horse; the current behavior is "interim". I'll come back to Vector-2022 when the later planned behavior is implemented. DavidBrooks (talk) 14:15, 8 August 2022 (UTC)

Search suggestions and keyboard accessibility in Vector 2022
(Reposted from enwiki's Village Pump)

One of my most common actions is to find a policy or guideline via WP: shortcut. Therefore I use the search box for this. Having recently upgraded to vector-2022, I've also adopted the Alt-Shift-F shortcut to search. I'm using Chrome 103 on Windows 10 Pro. If I happen to search while the mouse pointer is near the search box, "Enter" has the undesirable effect of activating the search suggestion which is indicated by the mouse pointer, rather than sending my query as-is to the search engine. This is an accessibility no-no. I pressed "Enter" to activate my keyboard input, not what's under the caret. If I need to move the mouse to avoid this situation, it defeats the purpose of keyboard entry. As soon as I enter a search term that produces suggestions, the mouse pointer immediately selects whatever's underneath it, and then "Enter" accepts that selection. But I'm not using the mouse.

Example: "Alt-Shift-F" MOS:GENDERID "Enter" took me to WP:MOS and WP:MOSBIO, successively, until I moved the mouse away from underneath the search box. Elizium23 (talk) 07:40, 7 August 2022 (UTC)

Contributions now requite two clicks - please allow customization of the top right
I think the skin is the step in the right direciton, but the fact that accessing my contributions requires two clicks is annoying. Ditto for rsome others. I understand the goal is to de-clutter stuff (good) but allow customization, please. Keep the current layout as default but allow users easy customization of what goes into the top right horizontal menu and what is hidden in the top right pull down menu please. Piotrus (talk) 11:56, 7 August 2022 (UTC)

High sidebar
I notice (using Vector 2022 in Simple English) that when the window is narrow (or more often for me, font is big) the sidebar slips to a position above the text and page header, to be alone with huge whitespace. Two things wrong with that:
 * It's too eager. The sidebar by the side would be quite tolerable even if the text width had to be diminished by another third.
 * When the sidebar really doesn't belong on the side, it ought to be off the page entirely. I notice that the sidebar contains links about this particular page, and about Wikipedia in general. When the sidebar vanishes, it ought to be replaced by two links in the header, duplicated in the footer; one for each of these two classes of link. The link for page details ought to show links to various things such as Sister projects, Cite this page, Print this page, Traffic, and other information about this page. The link for Wikipedia ought to show links for Contact, Help, My user page, Sandbox, Watchlist, and other things that are not about this particular page. Jim.henderson (talk) 19:49, 7 August 2022 (UTC)


 * This is in an interim state. Please see https://www.mediawiki.org/wiki/Reading/Web/Desktop_Improvements/Features/Table_of_contents#I_can't_see_the_table_of_contents_when_the_sidebar_is_open_on_tablet/mobile_device for details on our plans here. Jdlrobson (talk) 17:15, 8 August 2022 (UTC)
 * Ah. More particularly, Reading/Web/Desktop Improvements/Features/Page tools is what I'm getting at in my own clumsy language. How brilliant, to start work on my idea long before I thought of it. I am pleased to see competent minds running ahead of me on this matter. Jim.henderson (talk) 13:25, 9 August 2022 (UTC)

Redirect message
The redirect message should be dismissible and should also be shown in sections (e.g. en:Underfur redirects to en:Fur#Down hair, but no message is shown in the Down hair section). -- NGC 54  ( talk |  contribs ) 11:40, 10 August 2022 (UTC)

The search widget
In the search widget, there should be a technical wheel button for changing the settings available (the advanced search and the namespaces) on Special:Search (maybe the button opens a mini-window). I think that the presults should be as follow:
 * Featured article with 1 article
 * The most popular articles yesterday with 3 articles (in the right upper corner a button that links to https://pageviews.wmcloud.org/topviews/?project=en.wikipedia.org&platform=all-access&date=yesterday&excludes=)
 * Similar/Related pages/articles with 1–3 articles
 * Random article with 1 random article (in the right upper corner a button that replace the shown article)
 * Explore other projects should have buttons that send you to another 4 projects and so on (there are 12 wikis at https://www.wikipedia.org/, so 3 slides with 4 wiki each should be enough) -- NGC 54  ( talk |  contribs ) 11:58, 10 August 2022 (UTC)

Borders and backgrounds
When does Borders and backgrounds will be deployed on the first wikis? -- NGC 54  ( talk |  contribs ) 16:46, 10 August 2022 (UTC)

New ToC and a new wide sidebar design
It has become more difficult to read the text - the too bright field on the left distracts and prevents you from focusing on the text (in long articles) + the text is inconveniently asymmetrical on the screen (I turned the left sidebar and ToC and the text did not expand or the text column did not become centered - just an empty field on the left remained). I used the "new vector" skin for a long time, but now it has become uncomfortable to edit in it - I switched to the old vector (to somehow continue editing) where there is a gray stripe on the left (not so bright, easier for the eyes) and where the content is more centered on the screen. The skin has become uncomfortable, please confirm the usability of this part of the design on a larger number of subjects for laptops 1377x768. On large screens, you have made a column in the center, so do not worsen the user experience for laptops as well. It looks like there was an ad on the left, but it was hidden by an ad blocker and left an empty space. Also, for example, I reported Topic:Wsniusgsyzq7dp1l earlier that the left margin occupied up to a third of the screen if you enlarged the interface (since then it seems to have changed something and it has become a little narrower), this is definitely a problem of the new design and weak attention to laptops.Sunpriat 09:31, 12 August 2022 (UTC)

Support for Different Chinese Writing System
I saw the language switcher list "Chinese" only. However in Chinese Wikipedia, there are 6 different modes to trans characters and regional words automatically. Hope the new skin won't broke the transforming system, or maybe making all Chinese writing system (zh-cn, zh-tw, zh-hk, zh-sg...etc.) in the list will be better. --Reke (talk) 09:02, 13 August 2022 (UTC)