Talk:Reading/Web/Desktop Improvements

Typo?
At Reading/Web/Desktop Improvements the majority of wikis ... only editors can opt-in using Switch to old look in the sidebar (emphasis added) — should that be "opt in using switch to new look"? Pelagic (talk) 18:06, 20 July 2020 (UTC)


 * @Pelagic - good catch! Now fixed. To clarify, we're not adding a specific link when opting in but the preference is available in the appearance tab of user preferences OVasileva (WMF) (talk) 12:41, 22 July 2020 (UTC)

First impressions when deployed at euwiki
Hello! Today it was deployed at euwiki and I want to share some first impressions about what I have seen.
 * The design is something in between nothing. No real change, only some minor "improvements", so everything looks broken.
 * We have lot of pages using PAGEBANNER. You can see it at eu:Txikipedia:Ornodun or at eu:Laguntza:Sarrera. The feel is very bad, because it doesn't take all the wide BUT you know it should be wider because the top menu is wider.
 * Many things are going out from the right. Look at eu:Txikipedia:Azala or eu:Txikipedia:Ornodun
 * As the article reading box has disappeared, lot of things look "hanged-out" from nowhere. You can see it for example at eu:Ugaztun how the globalnotice, sitenotice and page-related icons (i.e. featured article) are taking a lot of space. If you read a very short article (eu:Fisiopatologia) this is further evident. The article content is less clear.
 * The footer (including categories) should be sitewide. Is not part of the article, is part of the infrastructure.
 * The sister projects links are now completely forgotten, making Wikimedia projects even less important. If you are trying to hide them from the sidebar they SHOULD be somewhere in the top of the page. THIS IS VITAL, is not something about esthetics, is something about WHO WE ARE and our Strategic Goals.
 * Top tabs are too crowded. This can't be the solution. It is so small area that the history tab is merged with the "Other" tabs. Loot at eu:Ugaztun.
 * Top tabs still have the "old look" and are now weird.
 * In our case, Txikipedia has its own logo. It should appear in every page, instead of the Wikipedia logo. This was changed using css, so it must be reflected.
 * There is more margin in the right that in the left. Not centering the content is something that will make people mad.
 * Special pages are a mess. Full width, top tab not aligned...
 * When editing a page with new code editor, things are not well aligned in the right side.

These is my first feedback. -Theklan (talk) 15:14, 22 July 2020 (UTC)
 * Some other improvements that could make this better:
 * images and infoboxes can break the layout from the right, so there's more space for text and this items are presented in a more relevant way.
 * when the sidebar is collapsed, image galleries may have full width, instead of being constrained to the fixed-width layout.
 * Categories layout is really poor. The fixed width limits the columns to two, and it makes it worst for having a global picture.

-Theklan (talk) 16:02, 22 July 2020 (UTC)


 * Hey @Theklan, thank you for your detailed feedback. We appreciate you taking the time to investigate the changes and we hope you will continue to give feedback as the project progresses. As you may know this is the first of many deployments. I will do my best to reply to the concerns you've raised:


 * 1) PAGEBANNER issues — in this case I think some clarification is needed. I looked at the pages you linked but am not understanding what the issue is. Can you please clarify?
 * The problem here is that PAGEBANNER took all over the wide of the page (well, not the sidebar), and this is cool. Now it is constrained to a very fixed space. PAGEBANNER may be a good solution when the sticky top-menu is deployed to show below it, but with the current configuration it is not more "part of the page" but "part of the text". Consider thinking on making it sitewide, the result will be better.
 * 1) Many things are going out from the right — ah yes, I see what you mean here. As far as I can tell this was already an issue for all users with screens smaller than ~1200px. If you look at those pages using Legacy Vector (eu:Txikipedia:Ornodun or eu:Txikipedia:Azala), and make your screen size smaller you will see the same issue. So I think in this case we should work on improving the flexibility of the content such that all users, regardless of their screen size or skin choice, can have a good experience.
 * I have to work also on this kind of things, some of them can be worked (Txikipedia:Azala is one of them). Also, I think Main Pages shouldn't have the same "content" mood and they should be wider.
 * 1) things look "hanged-out" from nowhere – if I understand this correctly you are commenting upon the lack of some sort've frame around the content. Later in the project we are planning to focus on visual design and part of that will include thinking about how to frame the content.
 * Yes, the frame issue. Well, it can help now to have a small line.
 * 1) the footer should be sitewide – we agree. As you can see in this prototype (link to prototype) that was the intended design. We are currently struggling with some DOM ordering issues that make this difficult to implement, but we will keep trying.
 * 2) sister project links – there are two separate issues here. Firstly we made a mistake in our deployment: for logged-in users the sidebar should be open by default, so those links will remain right there. For logged-out users the sidebar will be collapsed by default. However the data shows us that those links get clicked very rarely (link to data). So it would seem that we need better design solutions to expose those projects to people if we want them to engage with them. The sidebar links aren't quite working.
 * They are not working, and now they will work less, because they are hidden by default. The more I think about this, the more I see that they should go below the page title, but hiding them is just worst than not being pretty/evident.
 * 1) Top tabs are too crowded – this will be resolved soon once we move the search bar into the site header (link to prototype) (see this page for more details - link)
 * 2) tabs look weird/old – this will be addressed later on in the project with the visual design portion
 * 3) Txikipedia logo – what a cool feature, I am sorry that we have temporarily broke it. Are you in touch with the developers who worked on that feature? I think it would be possible for them to chat with one of the developers on our team to figure out how to get that logo back.
 * I was the developer. I will do it!
 * 1) There is more margin in the right that in the left - if you collapse the sidebar the content is centered. If the sidebar is open the content is offset to the right, same as it currently is in Legacy Vector (it is just more noticeable now since we're not filling that space in with gray). We did consider making the sidebar sticky (link to prototype) to make better use of that space, but have decided to defer that until later. The good news is that with the new layout you can collapse the sidebar, thus gaining more space for content on smaller screens.
 * 2) Special pages are a mess – yes, the situation is certainly not ideal at the moment. We wanted to allow Special Pages (in particular log-type pages) to be wider than regular pages, however we thought it would be best if the tabs stayed in place, making it easier to navigate between Article and History, for example. You can read more about our thinking regarding Special Pages here (link to page). If you have any ideas for how to improve this situation that would be great.
 * Categories, special pages and code pages can be wider, because they are not intented to be read.
 * 1) New code editor, things are not well aligned on the right – can you clarify what you mean here? Perhaps a screenshot would help.
 * The "Publish changes..." button right-limit goes some pixels to the right of the search bar.
 * AHollender (WMF) (talk) 12:38, 24 July 2020 (UTC)
 * -Theklan (talk) 21:56, 27 July 2020 (UTC)
 * @Theklan - re: fixing the Txikipedia logo - not sure if this helpful but one of our developers put together some information on the logos and how to update them.  OVasileva (WMF) (talk) 13:56, 29 July 2020 (UTC)

Irrelevant radiobox
Hi. There is a bug on global preferences, two radioboxes for legacy vector. IKhitron (talk) 01:22, 24 July 2020 (UTC)


 * @IKhitron - thank you for the feedback! We are aware of this bug and have been tracking this in T258581.  Hope to have a fix within the next couple of weeks.   OVasileva (WMF) (talk) 11:04, 24 July 2020 (UTC)


 * Thank you for your answer, OVasileva. Here is another one: global preferences do not do anything in this case, you can change the legacy vector preference in local wiki only. IKhitron (talk) 11:43, 24 July 2020 (UTC)


 * Seems to be this one: T258493. Stryn (talk) 07:39, 25 July 2020 (UTC)

Painful interwikis (dis)order
I like the new look, but looking for the article in a different language is a pain. The interwikis on the left used to follow the alphabetical order, but now it is an absolute disorder, it takes me too much time to find the interwiki for a given language. --Xabier Armendaritz (talk) 10:28, 24 July 2020 (UTC)


 * @Xabier Armendaritz - thanks for reporting this! Do you have a screenshot of this issue by any chance? This sounds like a bug - the changes within the project so far did not include any interaction with the interwiki links, so the expectation is that the order of links should not have changed in any way.  As a sidenote - we are currently planning on moving the interwiki links to a more convenient location at the top of the page as well - more info on that can be found on the features page: see language switching 1, and language switching 2.   OVasileva (WMF) (talk) 14:38, 24 July 2020 (UTC)
 * This is a known bug, and is not related to Desktop Improvements (it’s broken in old Vector as well). It’s tracked in T257625. —Tacsipacsi (talk) 15:05, 24 July 2020 (UTC)

Vector2
Can we please not retroactively rename Vector as "Vector Legacy"? There's years' worth of documentation and discussion that mentions Vector, and you want to say "from 2020 'Vector' now means something else". Just find a new name for the new thing, even if it's as straightforward as "Vector 2". Don't confuse things by usurping the old name. —Pelagic (talk) 16:15, 24 July 2020 (UTC)

+1. Andy Mabbett ( Pigsonthewing ); Talk to Andy; Andy's edits 18:21, 27 July 2020 (UTC)


 * Hi @Pelagic, @Pigsonthewing. Thank you for the feedback! When we first began this project, we had a decision to make - build a new skin or improve our current one. For technical and maintenance reasons (for more details, see our FAQ), we settled on the latter. This means that rather than a new version of Vector (with a different name), what we are building is improved functionality for Vector itself. We’ll be building these features over the course of the next 1-1.5 years. Technically, this is similar to previous features or projects that were added to Vector such as page previews, with the only difference that, this time around, there will be more of them. We chose the language of “Legacy Vector” because it signifies Vector skin as it was prior to us beginning this project. Does that make sense? OVasileva (WMF) (talk) 12:14, 28 July 2020 (UTC)
 * It makes sense, in that I understand what you're saying. But I don't agree that its a good course of action; as Pelagic says, this will sow confusion. Andy Mabbett ( Pigsonthewing ); Talk to Andy; Andy's edits 12:48, 28 July 2020 (UTC)

Отзыв
Довольно интересная и долгожданная идея.

Замечание: как вы можете заметить здесь с 150% масштабом, при скрытии и раскрытии текст статьи скачет по горизонтали. Это нехорошо для людей, которым желательно использовать такой масштаб страниц из-за проблем со зрением.

Комментарий: при использовании очень полезных скриптов часть из них формирует новые табы рядом с табами править/править код/история. В результате их становится больше и они ломают верхний блок, налезая на название страницы. Наглядно, см. скрин скрин. Либо нужно переписывать все скрипты, либо как-то сохранить предыдущий размер верхней полосы, чтобы он не ломался от дополнительных 2-3 табов.

ПС: Кстати, при 150% масштабе вторая проблема исчезает) Ailbeve (talk) 11:41, 27 July 2020 (UTC)


 * Hello @Ailbeve, thank you for your feedback. Regarding the tabs above the article title: soon we will be moving the search bar to the header which will open up space for the tabs. This should fix the issue you described. Please see this page for mockups: link to page, or you can view a prototype of this feature here: link to prototype. AHollender (WMF) (talk) 15:03, 27 July 2020 (UTC)

Why limit width of content?
".skin-vector-max-width .mw-content-container { max-width: 960px; }": I have 2K screen and content takes less than half of my screen :( Most Main Pages use two column design, so they look epecially trashy. --AS (talk) 14:41, 27 July 2020 (UTC)
 * Hey @AS, thanks for your question. The reason for limiting the content width is to provide a more comfortable reading experience. We've written a bit about our research and thinking here: Introducing a max-width. AHollender (WMF) (talk) 15:03, 27 July 2020 (UTC)
 * I came here to ask the same thing. With this answer, I'll switch from Vector to Timeless. Ainali (talk) 15:20, 27 July 2020 (UTC)
 * Strewth. "mw-content-container {max-width: 960px;" That is horrible. Please reassure us that legacy Vector will continue to be available and Vector 2 will be an extra choice. — GhostInTheMachine talk to me 17:23, 27 July 2020 (UTC)
 * Why is this in px and not em? Andy Mabbett ( Pigsonthewing ); Talk to Andy; Andy's edits 18:20, 27 July 2020 (UTC)

Thanks for the response above. Would the team perhaps consider adding an easy preference opt-out for the max-width? I can play around with CSS and pick it apart, but it'd be a whole lot easier to just have a preference for it, seeing as this seems likely to be a pain point for many users who are creating content rather than reading it. I've just tried the new Desktop Improvements on enwiki for the first time, and it was the first thing that immediately stood out to me as a "nope, don't like this" of the new theme. I like a lot of things about it - the new sidebar hiding and background look swanky! Naypta (talk) 18:49, 27 July 2020 (UTC)
 * Naypta thanks for checking it out and providing your thoughts here. I hope you will continue to follow the project and provide feedback. I agree that the limitation on the width of the content is going to be a pain point for many users, which makes it a difficult choice (and undoubtedly will be the reason why many editors will opt-out). I suspect that a full-width gadget or user script will emerge soon. One point however that I think is worth considering is this: there is extensive research showing that shorter line lengths provide a more comfortable reading experience and allow readers to comprehend and retain information better. It is the reason why so many major information websites follow a similar layout. While we still plan to conduct additional research, it seems like we can have relatively high confidence that this layout makes sense for the majority of users. Now if editors start using a layout with a different max-width (or no max-width at all), when editing articles they will not be seeing the same thing that readers will see when reading the articles. I don't know that this is inherently bad, but my inclination is that the closer the editing experience is to the reading experience, the better the articles will read. As you probably already know there are plenty of templates that break at small screen sizes, and I suspect part of the reason for this is because some editors have large monitors, and therefore these templates are not being tested at smaller screen sizes. So I guess in short: we fully support people being able to adjust the density/width of the content, but at the same time we wonder if there might be some tradeoffs to consider in terms of consistency between what is written and what is read. AHollender (WMF) (talk) 21:27, 27 July 2020 (UTC)
 * This really is sub-optimal for sites where you have to read a lot. Even sites with a lot of content that have a fixed max-width for the main element, have other elements that take up the space or simply, have less content. With Wikipedia pages, it's just empty, a white void with literally no use, surrounding tons of text. Someone on a 1800p display will have ~50% of their display just being empty! I am aware that fixed-width brings better readability but you're not really considering all the use-cases here, and the assumption that a consistent experience is equal to a better experience is false equivalence at best. --QEDK (talk 桜 enwiki) 21:51, 27 July 2020 (UTC)
 * I suddenly realize how long my (or some other users') paragraphs on discussion pages are. I'm not yet certain if that's a good thing. Nevertheless, it reduces the number of reasonably usable indentation levels, which might really be a problem on noticeboards. ToBeFree (talk) 00:55, 28 July 2020 (UTC)
 * Okay, it's not just discussion pages. I need a wide screen for en:WP:AIV, ideally one line per request, or it becomes hard to manage during busy times. ToBeFree (talk) 00:58, 28 July 2020 (UTC)

After some days of having this at euwiki, I must say that the reading experience is much better. Discussions, special pages and categories must be improved, but articles are now easier to read, especially in wide screens (you don't need to move the head). -Theklan (talk) 11:23, 28 July 2020 (UTC)

I also find the limiting width a bad move. I would understand if it was larger, but here it make the pages shrinkened for a even a normal sized screen, which mean way less content on a single page with large empty bands on either sides, and force to scroll more and more for the same content. Not to mention that in lots of pages the very small width forces left and right sided pictures way too close, making the amount of text on a single page even more diminished. I hope it will be changed for a larger one.--Aréat (talk) 16:31, 5 August 2020 (UTC)

The fixed format will ensure a more coherent design since every contributor will see how the images fit into the page. This decision was long overdue.--Codex (talk) 19:34, 5 August 2020 (UTC)

Preventing people, like this, from increasing the width of content, and deciding in their stead what is "a comfortable reading experience" is "paternalistic" : ''Paternalism is action that limits a person's or group's liberty or autonomy and is intended to promote their own good. Paternalism can also imply that the behavior is against or regardless of the will of a person, or also that the behavior expresses an attitude of superiority''. This width limit results into the creation of big empty spaces on the right and left parts of the screen. These spaces being of white color, they are dazzling. I would not be surprised if further research reached the conclusion that this is tiring for the eyes, harmful for the eyes, harming visual attention, resulting into a not more but less comfortable reading experience. Being an encyclopedia, Wikipedia is a reference tool. At times it is something you may want to read like a book, at times you just browse it to look for a specific information, like a name, a date, a mathematical formula, etc. Typically, when you need to remind yourself something you used to know but later forgot. I am not convinced that wasting screen space is the best way to do so. Whenever, for some reason, I want to restrict text width, I do so either by resizing the window, or by using Firefox's reading tool which I can adjust with my own preferences ( https://support.mozilla.org/en-US/kb/firefox-reader-view-clutter-free-web-pages ). Theo F (talk) 05:52, 6 August 2020 (UTC)

There are already some pages using column layout, in particular the title pages of each language Wikis. The columns being squashed by the width limitation look especially surprising. The need of scrolling for reading distracts way more than even blank borders around, and definitely more than just long lines. Maybe Wikipedia should adopt a long-standing practice of scientific articles? For the ease of reading, A4-page there is divided into two columns, and you don't need to turn pages twice as often, nor do you question yourself why half of the space is blank. In any case I strongly suggest that maximum width are an adjustable setting with an option to use a browser client window width. Глюкавый (talk) 10:28, 6 August 2020 (UTC)

The sidebar and alignment problems
The hide-sidebar I think is a good idea, but for me the opened sidebar looks broken now. The border would make this look better (sharper).

The whole layout with new sidebar and logo looks broken because nothing seems to aligns there:
 * The logo partially overlays top menu (if window is short or you have many tools there).
 * There is weird white padding between sidebar and content. And that margin doesn't equal to the one n the right.
 * Content is not aligned with top menu, nor with the logo.

For me the logo with text is just too long and this is causing problems. I think this just doesn't work with this layout. It just looks out of place. I've seen various non-standard layouts e.g. of Jen Simmons that just work together. Vector2 just don't seem to work together. Sorry.

One more thing. You could maybe make the new logo work if you move it out completely from the sidebar space to top (over top menu). Maybe also put the search bar on top as well. That would work much better for thin windows as you would see more article-actions (page history etc). Also the search-bar would be wider. I think the whole point of moving search bar from sidebar (old monobook) to the right (1st Vector) was to make the search bar wider. --Nux (talk) 22:26, 27 July 2020 (UTC)

PS: BTW. If you move the logo out of the sidebar you can make the hamburger a bit smaller. You can also put the "menu" word in there. There are studies that show that the hamburger icon is not universally recognized (probably even more of a case for the arrows). With menu word it would make more sense. --Nux (talk) 23:00, 27 July 2020 (UTC)


 * @Nux thank you for taking the time to look through the updated interface and provide detailed comments. I'm not sure if we've done a good job communicating this to people but this update is the first of many. As you've noted there are many different elements to consider on the page, and they all have a relationship to each other. As the project progresses things will fall into place more, and we will restore some of the harmony that we've temporarily lost. For example two of the next updates will be: moving the search bar into the header, and collapsing the user links into a menu. With these changes the top portion of the page will look more organized and clean. One of the biggest challenges for us is finding the right sequence to release the updates, because we know there is bound to be some weird states in between. I encourage you to take a look at our features page, as well as this page with some of our more bold ideas. I will also be working to try and communicate our future plans more clearly, such that people can more easily understand our plans.
 * @AHollender (WMF), thanks for the information. I've seen previous experiments and assumed this layout won. --Nux (talk) 19:27, 30 July 2020 (UTC)
 * I think I understand some of your ideas, and appreciate you taking the time to write them up. Would you be able to create some sort've sketch or mockup? I think it would be great to have that more as part of our culture when discussing interfaces. Cheers AHollender (WMF) (talk) 13:42, 30 July 2020 (UTC)

Below is a sketch of something I was thinking about. Unfortunately I don't have my mouse on vacation so this is a bit rough and one size only. When collapsed the sidebar and the menu-toggle button could be shrank with some animation maybe. Or maybe just don't use border for the button... Not really happy with how that button turned out. I'm sure a graphic designer will be able to figure something nice for that 🙂. In terms of a role it's a button, but it does looks better without a border and with a blue text color (like for links).

Back to the alignment problem... Note that in terms of alignment I kept the personal bar aligned to right to make it feel out of the article space (as it is not related to the article obviously). I also purposefully kept it aligned vertically to the left menu button (as they are both more or less about a generic navigation). Oh and the search bar is not stretched to full width, but I guess you could stretch it a bit more.

BTW. I don't think that collapsing the personal bar is needed. By default that menu is quite short and clean by itself and power users tend to keep important links in there (I remember this was a quite popular place for enhancements). So at least for me collapsing p-personal would not be a desired feature.

Cheers, Nux (talk) 19:27, 30 July 2020 (UTC)
 * Added a gradient version that looks more like article tabs so should be more obvious. Also X (cross) for closing is more standard. The cross -> hamburger animations are quite popular from a few years I think e.g.: . --Nux (talk) 18:52, 31 July 2020 (UTC) PS: I also changed the bell icon which seems not to conform to WCAG AA, but the human-user icon conforms to WCAG AAA.
 * Oh, also note that the content in my version is centred to the remaining space (excluding sidebar). Otherwise with sidebar opened content feels weirdly aligned to the left. I did a brief UX test on another user and the weird left alignment was the first thing she noticed and mentioned (without me saying anything about it and just asking which version she likes best). She also didn't have problems finding the search box (even though it was on top and on the left). --Nux (talk) 18:52, 31 July 2020 (UTC)


 * @Nux Sorry for being slow in following up here. I've also experimented with different options for the sidebar menu open/close button. I agree that having a hamburger menu in the header isn't necessarily the most clear, though I do think it's worth noting that many websites do it. And I don't think it's unclear enough to be problematic. Not a perfect solution by any means but probably good enough. Regarding your sketches, I think the challenge is where to put the Menu button when the sidebar is collapsed. I've attached an image below to show the previous solution I was considering. Also, regarding the sidebar always remaining fixed to the side of the screen, on wide screens this means there's a large gap between the sidebar and the content. AHollender (WMF) (talk) 19:43, 21 August 2020 (UTC)
 * Floating menu tab.png

Sidebar is not hideable for thin windows
Seems like there is a z-index problem. The sidebar toggle button is in `.mw-header` which is `z-index:1`. And `#p-personal` is `z-index:100`. So this makes the toggle button unclickable. You must make the window thin enough (or have a lot of actions in `#p-personal` like me). --Nux (talk) 22:44, 27 July 2020 (UTC)


 * @Nux - thanks for letting us know! I think this is the same bug as T258465, which we're hoping to fix soon.  Let us know if not and we can open a new task.   OVasileva (WMF) (talk) 12:17, 28 July 2020 (UTC)
 * @User:OVasileva (WMF), yeap, that looks to be exactly the same problem. Thanks. Top toolbar is wrapping to next line for me as well. --Nux (talk) 17:05, 28 July 2020 (UTC)

Vector 2.0 whitespace issues
At least on my screen (Firefox 78 for Mac, 1280x800 display, OS X Dock on the right side), there are some whitespace issues with Vector 2.0: The combination of these things moves the body of the text, which is the thing I most want to see, down by two or three lines, off the bottom of my screen. Please fix. Jonesey95 (talk) 00:07, 28 July 2020 (UTC)
 * 1) Compared to Vector, there is an extra centimeter of whitespace between the sidebar items on the left and the page body text. It looks like a weird void.
 * 2) I see almost a centimeter of extra, unwanted whitespace on the right side of the body text.
 * 3) I see about half a centimeter of new, unwanted whitespace between the links at the top right (talk, prefs, etc.) and the search box.
 * 4) Hiding the sidebar with the back arrow that is not a back arrow does not make the content wider; it just shifts it to the left. Why would I hide it?

One more bug
A lot of people are complaining since today that the new design was turned on without any action from their side. IKhitron (talk) 14:06, 28 July 2020 (UTC)


 * @IKhitron - Do you know which wikis this is coming from? For a set of early adopte r wikis, we are turning the design on by default as per community consultations and approval on those individual wikis.  Currently, the changes should be available by default for euwiki, hewiki, fawiki, frwiktionary, and ptwikiversity.  The changes can be turned off via a link in the left menu or by going to user preferences.   OVasileva (WMF) (talk) 14:43, 28 July 2020 (UTC)
 * I see. Hewiki. Well, all of them do not like the new design, because of a lot of empty space. I've published a css code that removes this space, but they are right, noone should suffer without asking this. Maybe you needed to start a discusdion with community, weeks before the cgangd, explaining exzctly what changes will be done. For example, I still do not know the full list of changes, only what I can see. I'm affraid that this situation will lead to demand to remove the wiki from the list.

Errores y sugerencias

 * Sorry for write in Spanish, I didn't speak English good

He activado la opción en las preferencias de la wiki en español y gallego (no funciona como preferencia global, pero ya lo han dicho arriba) y he detectado varios errores:
 * En las páginas especiales (incluido historial) no funciona el límite de ancho.
 * El enlace "(revertir)" de los diffs no deja un resumen de edición predeterminado.
 * El cuadro de búsqueda se mueve un poco a la izquierda en las páginas especiales.

Y dejo como sugerencias: Fin de la página/End of the page.
 * Hay un triple salto de línea al final de la página. Además, la línea de separación es gris, lo que hace que el "footer" parezca parte de la página:

This page was last edited on 27 August 2024, at :.

Text is available under the Creative Commons Attribution-ShareAlike License; additional terms may apply. See Terms of Use for details.


 * Debería aparecer sin los saltos de línea y con la línea en azul para que se vea claramente que es el fin de la página:

Fin de la página/End of the page.  ─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────── This page was last edited on 27 August 2024, at :.

Text is available under the Creative Commons Attribution-ShareAlike License; additional terms may apply. See Terms of Use for details.


 * El contenido de la página es muy estrecho y hay mucho margen. Eso hace que ciertos gráficos y tablas se salen de la pantalla. (ejemplo 1, ejemplo 2, entre otros) Debería cambiarse el ancho de 960px a 1075px (por lo menos a 1060 px). Yo lo he configurado así en mi common.css en español y gallego (que es donde tengo activada la opción) y se lee mejor. USI2020 (talk) 17:58, 28 July 2020 (UTC)
 * Hola @USI2020, gracias por tus comentarios!
 * Primero, disculpas porque mi Castellano tampoco es muy bueno :)
 * Unas respuestas y pensamientos:
 * En las páginas especiales (incluido historial) no funciona el límite de ancho:
 * Generalmente, las páginas especiales no se leen de arriba a abajo como el texto de un artículo - se miran más rápidamente, así que necesitamos un diseño que permita este uso.  Pensamos que es mejor tener el ancho completo y que eso facilitaría la lectura mas rápida de la información de este tipo (similar a un spreadsheet de Excel)
 * El enlace "(revertir)" de los diffs no deja un resumen de edición predeterminado.
 * Tienes una captura de pantalla aquí? Creo que esto no está relacionado con nuestros cambios, pero necesitaría más información para confirmar.
 * No tengo, pero para comprobarlo basta con ir a un diff al azar y presionar revertir sin guardar los cambios. El resumen de edición queda vacío. Si pruebas a hacerlo con esto desactivado deja el mensaje en Mediawiki:Revertpage: «» USI2020 (talk) 10:32, 29 July 2020 (UTC)
 * El cuadro de búsqueda se mueve un poco a la izquierda en las páginas especiales.
 * Esto si que es nuestra culpa. Ahora estamos moviendo el cuadro de búsqueda un poco más arriba en la página y esto resolverá este problema. Puedes leer más sobre esto aquí: T249363.  Este cambio debería estar listo en más o menos dos semanas.
 * Sobre el final de la pagina:
 * También estamos trabajando en esto: nuestro plan inicial era que la parte del final también fuera gris (como en el diseño anterior), pero eso era técnicamente un poco complicado. Actualmente estamos discutiendo nuestras opciones aquí. Este cambio podría necesitar un poco más de tiempo, tal vez un mes más o menos. OVasileva (WMF) (talk) 10:11, 29 July 2020 (UTC)

A Bug with the desktop improvements mode
Hai, I experienced a bug when enabled the new desktop improvements. I don't know whether it is a bug or my mistake. I am posting screenshots of this thing.The problem is the content is limited to a small with area. As you can see in the screenshot on the left side the contents box coming right side images are coming and the text in the article is shrinked to a small area of 350px wide. So the thing endup like in the screenshot at |the phabricator task.I am using Firefox 78 on Fedora 32 with KDE Plasma 5.19.3 I don't know how to fix this. If anybody know the solution plz help.Ranjithsiji (talk) 13:33, 29 July 2020 (UTC)

Main Page
Hi! A small suggestion, I think the Main Page should be full width as is the case with some namespaces.--Ghybu (talk) 16:41, 5 August 2020 (UTC)


 * Noted, we'll discuss this. Thank you, @Ghybu! SGrabarczuk (WMF) (talk) 16:54, 5 August 2020 (UTC)

Keep large pages when source editing
Hello, At first I was surprised by the new presentation. Now I admit that it makes wikipedia easier to read, just like a LateX file. However, would it be possible to keep the full screen when editing a page with the code editor? I think it's a shame to lose space in that mode.

Thanks. --Le Petit Chat (talk) 16:56, 5 August 2020 (UTC)


 * @Le Petit Chat, thank you for this idea. We will take a closer look. SGrabarczuk (WMF) (talk) 14:08, 11 August 2020 (UTC)

Logo no longer localized with legacy vector turned off
I went to el.wikipedia.org and turned off legacy vector in the user preferences. The logo in the upper left used to have the Greek name "Βικιπαίδεια" but now it has the English name "Wikipedia". This is very disconcerting, can it be set back somehow? I would like to keep the rest of the changes to see how I like them. Thanks! -- ArielGlenn (talk) 05:19, 6 August 2020 (UTC)


 * @ArielGlenn - Thanks for your feedback! This is temporary.  We are currently working on getting all of the new logos ready across all wikis.  We're hoping to add elwiki to T258552, which means it should have the new logo localized within the next couple of weeks.   OVasileva (WMF) (talk) 07:08, 6 August 2020 (UTC)

New text width slightly too narrow
Not a bad idea to have set a limit to page widths for large screens, however the current text width for the French Wikipedia looks too narrow, as even a 12.4" display with a 1366 x 768 resolution leaves 15% empty stripes on each side, and makes images and tables collide into each other on scientific pages. The standard width should not be narrower than most common laptop displays, otherwise too many pages will need significant rework, which might be done for TV shows or videogames, but will be very unlikely for molecular biology or nuclear physics.  This change will hardly be applicable to the German Wikipedia anyway: look at the average size of German infoboxes!

In addition, the edition window should not be constrained: I support previous comment that we should be able to enjoy a large screen when we have one!

Thank you, Bob Saint Clar (talk) 05:21, 6 August 2020 (UTC)


 * @Bob Saint Clar - thank you for your feedback! We just wrote a little bit more about our rationalization on choosing this particular width for text - please check our our FAQ as well as the limited content width page. That said, we do want to explore better ways of displaying non-text content such as larger tables and are hoping on iterating on this in the future.  For editing, we are considering moving the source editor to full width.  For visual editing, however, we think that having a standard size for readers and editors despite screen sizes is a benefit.  It will allow editors to see the exact way people will read the content afterwards, which can lead to better formatting across all content.   OVasileva (WMF) (talk) 11:31, 13 August 2020 (UTC)

Nouveau style (Wikipédia Fr)
Personnellement, je trouve que la récente mise à jour du style de Wikipédia n'est pas nécessaire, car elle ne présente aucune utilité indiscutable. Je reconnais l'effort envisagé pour pouvoir replier le menu, mais je ne trouvais pas celui-ci gênant. Cela n'a donc rien ajouté à l'aspect pratique de l'encyclopédie (ça a d'ailleurs plutôt enlevé des choses : par exemple, le nouveau CSS ne s'adapte pas aux dimensions de mon écran, ce qui fait que j'ai une marge inutile à droite quand je ne replie pas le menu). De plus, l'icône du site s'y trouve rétrécie, mais cela me dérange moins. Pour moi, cette modification est à revoir. --Hérisson grognon (talk) 09:20, 6 August 2020 (UTC)
 * Bonjour. Si l’idée de départ est intéressante (réduire la longueur des lignes pour améliorer la lisibilité), la mise en œuvre est décevante et ressemble à la version pour mobile. Sur un écran large 16/9 de 27 pouces, maintenant courant pour un pc de bureau, on se retrouve avec deux marges blanches et la largeur utile est réduite à 1050 pixels (sur 1920). Wikipédia devrait-il être optimisé pour lecture sur un écran de 15 pouces ? Dans le cas d’un écran large, on est conduit à réduire la largeur de la fenêtre pour visualiser Wikipédia. La réduction de la longueur des lignes aurait dû être accompagnée d’une réflexion sur la mise en page. Il serait possible d’employer utilement les marges pour y placer par exemple le sommaire, l’Infobox, les illustrations, les notes et références... En l’état la nouvelle mise en page n’est pas un progrès. Il serait intéressant de compter les utilisateurs qui, comme moi, ont immédiatement modifié leurs préférences pour retrouver l’ancienne mise en page. Cordialement.--Philippesalv (talk) 11:30, 6 August 2020 (UTC)
 * "Il serait intéressant de compter les utilisateurs qui, comme moi, ont immédiatement modifié leurs préférences pour retrouver l’ancienne mise en page." Yes, it could be interesting. Patriccck (talk) 11:42, 6 August 2020 (UTC)
 * ✅ Utiliser l'ancienne version de Vector (Use the old version of Vector) — DePlusJean (talk) 19:33, 6 August 2020 (UTC)
 * Bonjour. Cool, j'apprends que les utilisateurs enregistrés peuvent revenir à l'ancienne version. Et pour les millions d'autres qui, simples lecteurs, n'ont jamais à s'enregistrer, même pas un petit cookie pour stocker une préférence de cet ordre ? Ou alors ils n'ont qu'à dire amen aux modifications cosmétiques et la fermer (si c'est ça la philosophie Wikipédia, bien sûr) ? Cordialement, Xavier 90.6.243.101 12:07, 7 August 2020 (UTC)
 * Je préfère également l'ancienne présentation. L'actuelle ressemble à celle de la version pour mobiles. Je trouve la colonne de gauche (Accueil, Portails thématiques, Article au hasard, Contact, etc.) trop claire (insuffisamment grisée) ce qui rend la page éblouissante. Lorsque je clique afin de la masquer, la zone d'affichage du texte ne rélargit pas, la largeur de la marge de droite augmentant d'autant que celle de gauche se réduit. Cordialement, Olimparis (6 août 2020).
 * Je suis retourné sur "l'ancien" vector. Ahhhhh j'ai de nouveau une page commplete, et pas 2 bandes blanches immondes. Vivi-1 (talk) 08:24, 10 August 2020 (UTC)
 * Hello — please excuse my message in English. I understand that the amount of whitespace on the screen can feel frustrating or even make the page look broken at first. My request is that you give it a chance — maybe a few weeks even, before you come to a conclusion about whether or not it's a good idea. The content width was arrived at after reviewing multiple research studies on readability, and reviewing many popular content websites. We will, as some of you have suggested, be experimenting with using those margins for a fixed table of contents, article tools, or eventually content-related things like images and infoboxes. So in short, we are far from done. We have written up some additional details about content width and white space on our FAQ page (🔗 link).
 * We appreciate all of your feedback and suggestions and hope that you will continue to follow along as the project progresses. Thanks AHollender (WMF) (talk) 16:43, 13 August 2020 (UTC)

White spaces
Hi, I think there is (especially on the right) too much white space. It looks like space for advert (image). Why can't the text be stretched anymore? Editing in such a small window is not good for me. --Patriccck (talk) 11:34, 6 August 2020 (UTC)


 * By all means, nobody is even thinking about allowing adverts to appear on Wikimedia wikis! Our explanations on why can't the text be stretched anymore, see our FAQ. SGrabarczuk (WMF) (talk) 14:11, 11 August 2020 (UTC)

Reduce the "Limiting content width"/ Much larger content container
Hi, I'm from the French Wikipedia. And I see a lot of negative reaction on French Wikipedia after the implementation of the first serie of Desktop Improvements. The more controversial element is the "Limiting content width". For my opinion, you should try to be more consensual and less ambitious on this feature, because on others Wiki, there will be much more negative reactions, based on the history of the relation between WMF and the different wiki. I think it's the more important element, but there are a other reason : the "Limiting content width" need to be associe with lot of work by the community to ajust element which are not responsive, and it will need lot of time to the different community to do those things.

I'm advice, it's better to have a much larger content container for large screen and temporarily have a larger content container to give time to the community to adapt. Nouill (talk) 12:52, 6 August 2020 (UTC)

Going back to the old style for IPs
Hello,

I’m often using the French Wikipédia as an IP, mainly for just reading articles. I was very surprised today to find that the new interface had been enforced without any warning (at least to the average, not logged-in reader). No banner, and especially no way to go back to the old version where you can use the full width of your screen. Worst, it isn't effective on all pages, you can browse WP and then suddenly go back to the old interface (Joy and happiness in my heart!) and then another click, and there is the new interface again (Nooooo!). It's pretty disrepectful for users to implement that change without any warning, and worst, it lacks a "go to fullscreen version" button.

Could we please have a "go to fulscreen version" button ? Thanks 176.186.245.230 15:15, 6 August 2020 (UTC)
 * While I personnally chose to use the new version, I second this request. Accounts are for editing and discussing, not for reading; the common (i.e. unlogged) reader should have as much choices as the logged editor when it comes to reading comfort. For example Reddit has this under the url old.reddit.com. Thank you for your work! --GrandEscogriffe (talk) 19:18, 7 August 2020 (UTC)
 * Hi @176.186.245.230, @GrandEscogriffe... Thank you for your feedback! You raise a few good points - I’ll try to do my best to answer all of them.  First I’d like to note that the new version of Vector, and the maximum width in particular, is very helpful for readers, as studies have shown that shorter line width increases text retention and readability - feel free to check out the rationale on the feature page, which also includes a brief literature review of previous studies on this.
 * That said, in general, I also completely agree that logged-out users should be able to modify their experience to their needs in a similar way to people who are logged in. We have future plans for a variety of logged-out preferences that would allow for us. Unfortunately, due to the way we currently cache our content, these changes are very difficult to implement and would require a complete rearchitecture of our caching system.   In short, while we have this included in our future plans, we don’t yet have the technical ability to make it happen.
 * Finally, I wanted to address the issue of switching back to the old version for some pages.  This is also due to content caching.  When we deploy a new change, it takes it a few days to propagate across all pages of the wiki.  After a maximum of 7 days, you should be seeing the new version of the pages only. OVasileva (WMF) (talk) 14:09, 10 August 2020 (UTC)

Comments on line length, content separation and readability
The idea that shorter line lengths are better does not agree with literature. Longer lines = longer read speed. Dan Luu commented on this: https://twitter.com/danluu/status/1115708058238251008 More over, if you want to increase readability, why not instead increase the font-size? The only way I can salvage the redesign over the old one is by increasing the zoom size to +150%. (But the fonts become too big). Please don't deploy as is. I'm barely on a 24" screen and the redesign is wasting around 50% of my screen real estate. Also, the side bar separation which was clearly visible before is now being faded. Where there used to be gray = sidebar, white=main article, there is now a background grey, a floating sidebar, a __barely visible___ vertical separator line, and another floating article. On the old version, when you scrolled enough to not see the sidebar text anymore, the separation between two was clear and it helped actually anchor the reading. Now the text is just floating in a sea of white, with some kind of small, fixed size side gutter to the left and right on the sides in very light grey.


 * The statement : "The idea that shorter line lengths are better does not agree with literature" is interesting. In fact why do people want to "improve" or to smoothen the learning process in the first place, when an increasing amount of literature points to the fact that learning is deeper when the student struggles with the content ? If the reading process is too smooth, too involuntary, it might well be that the memorization is less deep than when the student needs to voluntarily seek information, by taking decisions on where to focus his eyes on a larger screen, as is the case in the Where is Wally/Waldo? books. Theo F (talk) 11:40, 7 August 2020 (UTC)


 * Hi @Theo F - thank you for your feedback! There actually is some literature that concludes that shorter line width actually improves the retention of information as well.  In particular, we looked at an eye tracking study from the IBM Center for Advanced Learning which found that participants reading paragraphs of narrower width had higher retention of content than participants reading wider paragraphs.  Similar results were also seen in a more focused study on people with dyslexia.  Please refer to the Readability section of the limited width feature description page for a list of some of the other literature used for our rationale for deciding on this particular line width and how it relates to the number of characters per page.  OVasileva (WMF) (talk) 14:33, 10 August 2020 (UTC)


 * I think the Wikipedia article referred to in the #readability section you mention, could be wrong when it ( en:Line length ) says "Studies have shown that short lines are often preferred over long lines by study participants, likely because they feel more at ease with format, which contradicts research suggesting longer lines are best for quick reading". In fact this is not a contradiction, it is consistent. In order to deepen memory, one needs to feel uncomfortable. There is no such thing as a free lunch. If you want to be a good learner, this is going to be a hard, "uneasy" work. Theo F (talk) 07:37, 11 August 2020 (UTC)


 * Also, in the case of narrow paragraphs, shouldn't the brightness of the unused right and left parts of the screen be adjusted in order to be lower than, or to match the brightness of the middle of the screen, or otherwise isn't the eye going to be distracted by bright dazzling white spaces on the right and left ? Isn't the eye going to get tired, in an ophtalmologic sense ? The screenshots displayed at Reading/Web/Desktop Improvements/Features fail to show those white spaces. They do not reflect what happens on a wide screen. Theo F (talk) 09:01, 11 August 2020 (UTC)


 * Reading the paper Theo F linked on Wikipedia one gets the impression that 30 years of research have generated enough studies to cherrypick support for any assertion about line length. Wouldn't it be then a better choice to let users who prefer shorter line length resize their browser window, instead of messing it up for the rest of the users? 93.136.184.51 19:05, 12 August 2020 (UTC)


 * Hey, I think there is an important clarification to make when discussing the Tweet from Dan Luu and the research paper referenced. That study, "The influence of font type and line length on visual search and information retrieval in web pages" (link), researched line lengths of 55, 70, 85 and 100 characters per line (cpl). Our current width limitation of 960px results in line lengths between 100 cpl (when next to an infobox) and 150 cpl (when uninterrupted by any inline elements). We are therefore at, and beyond, the upper range of what was studied. The study did find that task performance of finding a given link (what they call the "visual search task") was fastest with 85 and 100 cpl. And that for the reading task they found no significant difference among the lengths (however several other studies have found better speed and retention at the smaller end of that spectrum). Also worth noting that on the subjective preference question the majority of participants expressed a preference for 70 cpl. What can we make of this research? The conversation I think we should be having currently is about line lengths far outside of that range, and whether or not we think they provide a good experience. Unfortunately I have yet to find any research on line lengths of 300 or 400 cpl, which is an experience anyone with a wide monitor might easily get on Wikipedia. Perhaps we could assume that given all of the research is within the 35–100 cpl range, and that most major information sites are within that range, we could have some confidence that it's a good starting point. Of course it would be better if we could find research, or conduct our own, about what happens above that range. Regarding some of the other questions raised above: we have just written up several answers to these questions in our FAQ section. Please visit https://www.mediawiki.org/wiki/Reading/Web/Desktop_Improvements/Frequently_asked_questions. Thanks AHollender (WMF) (talk) 22:31, 13 August 2020 (UTC)

Nouvelle présentation pas du tout adptée
La présentation en mode vertical n’est pas du tout adaptée aux écrans horizontaux des ordinateurs !!! 151.127.32.46 18:23, 6 August 2020 (UTC)
 * Je préfère l'ancienne présentation ... _ ( Paille-en-Queue (talk) 18:30, 6 August 2020 (UTC) ) ...
 * Moi aussi! --Jwh (talk) 19:51, 6 August 2020 (UTC)
 * Je préfère également l'ancienne présentation. L'actuelle ressemble à celle de la version pour mobiles. Je trouve la colonne de gauche (Accueil, Portails thématiques, Article au hasard, Contact, etc.) trop claire (insuffisamment grisée) ce qui rend la page éblouissante. Lorsque je clique afin de la masquer, la zone d'affichage du texte ne rélargit pas, la largeur de la marge de droite augmentant d'autant que celle de gauche se réduit. Cordialement, Olimparis (6 août 2020).
 * En fait, la largeur limitée n'a pas été développée spécifiquement pour les écrans verticaux. Pourquoi nous avons déployé cela - consultez notre FAQ et une page plus détaillée décrivant uniquement cette fonctionnalité. Aussi, @Olimparis, merci pour votre avis sur l'arrière-plan de la barre latérale! SGrabarczuk (WMF) (talk) 14:18, 11 August 2020 (UTC)

Some first impressions
Hey there, aren't you guys rushing things a little bit? This is not a finished work. Do not present an unfinished work to the readers (and the editors) if you want them happy with it. First there is a clear issue with symetry. You have to collapse the toolbar to get a symetrical page with empty columns on both sides, but nobody wants his toolbar collapsed and certainly not an editor. I know once you start scrolling down the toolbar disappears but as they say, the first impression matters doesn't it ? There are other issues including for example bits of text squished into a tiny fraction of the screen between an illustration and an infobox, which you just can't describe as "comfortable to read" in any way, and large tables with plenty of content that clearly need more than 60% of the width of a screen to be comfortable to read, and become quite unreadable when they are further squished by an image or an infobox. You guys, I'm afraid, have to solve this kind of tiny issues BEFORE you deliver a new page layout. It might not look like a big deal, but it is worrying that some editors (including myself) are already turning back to the old style. If some editors start feeling that making it easier for the reader comes with making it trickier for them, it would be a huge failure on your behalf. Please put more time in experimenting with your work before you make it the standard for all wikipedia users. Thanks for your work anyway, Toghebon (talk) 19:01, 6 August 2020 (UTC)


 * @Toghebon, thank you for this comment! SGrabarczuk (WMF) (talk) 15:52, 11 August 2020 (UTC)

IT'S HORRIBLE !!!
Hi.

I've discovered this new appearence. It's horrible and no easily usable. Please restore the previous appearence. --ComputerHotline (talk) 19:14, 6 August 2020 (UTC)


 * @ComputerHotline, thanks! Could you elaborate more: how this change affects the way you interact with a wiki? Why isn't this usable for you? SGrabarczuk (WMF) (talk) 15:55, 11 August 2020 (UTC)

First impressions
The new appearance leaves an empty space, a few centimetres wide on the right side of every single article. Is there any way to fix this ? Yoyo360 (talk) 19:34, 6 August 2020 (UTC)


 * Hi @Yoyo360 - thank you for your feedback! Are you referring to the space between the menu and the article text?  If so, we are planning on fixing this in the next couple of weeks - you can track our progress on phabricator. Otherwise, the space on the right and left side of the text is expected - we have limited the width of the text to provide readability of the content.  You can learn more about our rationale on the feature page.
 * OVasileva (WMF) (talk) 14:34, 11 August 2020 (UTC)
 * OVasileva (WMF) (talk) 14:34, 11 August 2020 (UTC)


 * Hi @OVasileva (WMF) ! I was referring to the space on the right side of the screen. From what I understand it is actually meant to be there, but I think it is really weird to have a space completely unused. If the central space is used for the main content and left space for the menu, you should put something on the right as well, as on Twitter for example. 109.209.19.70 17:18, 11 August 2020 (UTC)

Trop étroit
La réduction de la largeur n'est vraiment pas une bonne idée, je trouve. On se retrouve avec des écrans d'ordinateur dont à peine la moitié de la largeur est occupé par du texte, ce qui oblige à jouer sans cesse de la molette pour lire alors que l'ancien affichage offrait davantage de contenu sur une même page. Les infobox et les images de part et d'autre du texte entre davantage en collision, réduisant davantage encore la quantité de texte affiché sur une même page, ce qui est particulièrement frustrant quand on voit de large bandes vides à gauche comme à droite. C'est d'autant plus dommage que la seule justification avancée est qu'avoir un même affichage sur ordinateur et sur tablette serait nécessairement une bonne chose. Non. En quoi est ce bien ? Avoir un rendu un peu différent en fonction du matériel utilisé est normal, et c'est absurde de priver les utilisateurs de l'un (la grande largeur d'un écran) sous prétexte que les ceux de l'autre n'en bénéficie pas autant. C'est du nivelage par le bas. Les tablettes et mobiles ont des avantages comme par exemple les gyroscopes intégrés, que n'ont pas les ordinateurs. Ce n'est pas pour autant que les applications en enlève l'utilisation sous prétexte que les ordinateurs ne l'ont pas. Ça n'a pas de sens de forcer à ce point une utilisation commune pour du matériel aussi différent au détriment des utilisateurs. J'espère vraiment que vous tiendrez compte des retours présents sur cette page. Cordialement.--Aréat (talk) 19:42, 6 August 2020 (UTC)
 * Do agree, nivelage par le bas! --Jwh (talk) 19:53, 6 August 2020 (UTC)
 * Same for me. Definitely not an improvement..--Damned (talk) 19:56, 6 August 2020 (UTC)
 * Je trouve la colonne de gauche (Accueil, Portails thématiques, Article au hasard, Contact, etc.) trop claire (insuffisamment grisée) ce qui rend la page éblouissante. Lorsque je clique afin de la masquer, la zone d'affichage du texte ne rélargit pas, la largeur de la marge de droite augmentant d'autant que celle de gauche se réduit. Cordialement, Olimparis (6 août 2020).
 * Exactement le même avis qu'Aréat. --89.156.216.137 20:18, 6 August 2020 (UTC)
 * Même avis également. — Vincent Lefèvre (talk) 21:49, 6 August 2020 (UTC)
 * Si encore le système permettait de basculer d'un mode lecture réduite à écran cinéma, ce serait toujours mieux que rien. En l'état je ne vois pas l'intérêt. Jpgibert (talk) 11:41, 7 August 2020 (UTC)

Something I do not understand is: why don’t you let users who find it hard to read wide paragraphs reduce the size of their window, use the zoom function of their browser, or use the reader view? Before this change, it was possible to reduce the wideness of the paragraphs using one of these methods; now, it is impossible to revert it and enlarge them — unless you are logged in, of course. There something strange in reducing the wideness of paragraphs now that many people use 1920px-wide screens… Thanks --Rükükü Stash Stash (talk) 07:28, 7 August 2020 (UTC)


 * Idem, la barre blanche d'espace inutilisé à droite me perturbe beaucoup trop, c'est désagréable, inesthétique, un gâchis monstre d'espace et pas du tout pratique puisque ça limite le contenu à lire sur la page. Et mon ordinateur portable n'a pourtant qu'un écran de 17 pouces. Je suis repassée à l'ancienne version à cause de ça, tout les autres changements ne me posent pas problèmes, j'aurais même pu en apprécié certains, mais cette limitation de la largeur de la page ? Une erreur. Pas du tout intuitif, tout le contraire. --Zeynel (talk) 10:14, 8 August 2020 (UTC)

Je suis un simple lecteur de Wikipedia, j'ai retrouvé ce très vieux compte pour pouvoir donner du feedback sur cette nouvelle interface, et pour dire que la grande barre blanche à droite est un gâchis d'espace, pas même utilisé pour y mettre les images. Je n'ai pas réalisé d'étude académique sur le nombre optimal de mots par ligne, mais rendre les pages plus étroites n'améliore rien du tout, resserrer tout rend les choses plus confuses au contraire. Je n'ai pas d'avis sur les autres modifications, mais si les retours des simples lecteurs sont appréciés, alors revenez en arrière sur le Wikipedia francophone, et n'implémentez pas ça sur les autres langues non plus. Merci d'avance. Xerbias (talk) 20:55, 8 August 2020 (UTC)


 * Hello — please excuse my message in English and my delayed reply to this thread. The motivation behind limiting the content width is to improve the reading experience, particularly for people with wide screens. The research we have reviewed recommends line lengths around 45–75 characters per line. The upper limit we have seen from research, or found on other popular information websites, is around 120 characters per line. Research shows that above this limit there are detrimental effects to speed, comprehension, and retention of information. If you take a look at some of the popular websites you use I expect you will find a similar width limitation. So we believe that is the correct default experience, even if it results in white space on the sides of the screen. Further along in the project we will be experimenting with putting a table of contents and/or article tools in that white space. I encourage all of you to take some time — maybe a few weeks — and give the new layout a chance. We have already heard from some editors that after a week or two of adjustment they are liking the new layout and find it easier to read. Of course if you have a strong preference for full-width content that is your right. A team member has made a userscript that adds a button to toggle the width of the content: https://en.wikipedia.org/wiki/User:Jdlrobson/vector-max-width-toggle.js. Lastly, we appreciate your feedback and hope you continue to share your observations and opinions. I also ask that you review the notes we've collected here so that you have the full context of our thinking: https://www.mediawiki.org/wiki/Reading/Web/Desktop_Improvements/Frequently_asked_questions#Why_is_the_width_of_the_content_limited?_Why_is_there_so_much_white_space?. Thank you AHollender (WMF) (talk) 16:58, 13 August 2020 (UTC)


 * Thanks for the answer. I'm always logged out when reading Wikipedia, so I care how it looks for the default user. On popular websites, there is stuff in columns around the text. If this has to go on, I strongly suggest you put everything that is not the article's text on the empty side, because it can reduce the size of the line way too much, which is not what you're looking for. An example : https://fr.wikipedia.org/wiki/R%C3%A9publique_d%C3%A9mocratique_finlandaise The infobox and the picture should be on the side, then, and length of the line would be alright. This is the priority to fix before implementing it further I think. Xerbias (talk) 18:02, 14 August 2020 (UTC)

Please stop!
Please stop inventing concepts that are useless. You get to dislike basic Wikipedians, those who work on the core of wikipedia: content. Let us work! If you want to make changes, let them be approved by a qualified majority and not by a small group disconnected from reality. --Archaeodontosaurus (talk) 20:04, 6 August 2020 (UTC)

Suggestions about font-size and infobox position
Hello!

Firstly, thank you for these welcome interface improvements.

To further improve readability, it may be worthwhile to slightly increase the text size and line spacing.

On the other hand, it is true that the presence of large white margins is a bit disturbing, especially with large screens. This space could be used to insert some of the templates that are common in most wikis. For example, infoboxes could be positioned in the right column at the beginning of the article.

Regards, Géodigital (talk) from French Wikipedia, 09:12, 7 August 2020 (UTC).
 * This space could also be used for the references: they would be better contextualized and the reader would not need to go down to the reflist section and then go up to where he was reading. --Daehan (talk) 10:02, 7 August 2020 (UTC)


 * Hey, thank you for your observations and suggestions. I apologize for my delayed reply. I fully agree on all points:
 * we should experiment with font size and line spacing. We're assuming that those changes would be more controversial than line-length, but maybe that's not the case.
 * we should experiment more with page layout, particularly regarding the table of contents, infoboxes, and references in the margins. There have been some great mockups submitted by contributors on this topic: https://commons.wikimedia.org/wiki/File:Annotation_2020-07-30_0xc80607.png and https://imgur.com/FVN98xx
 * I hope you all will continue to follow along as the project progresses and continue providing your helpful observations and opinions. Thanks! AHollender (WMF) (talk) 17:31, 13 August 2020 (UTC)

Freeze top pan
Hello,

Thank you for the new interface.

A direct consequence is that long articles are longer to scroll down, and consequently to scroll up. It is especially anoying to have to scroll up to the search bar, both for user and reader.

So, would it be possible to freeze the top pan that includes (or will include) logo, search bar, personal links (user, talk, preferences, beta, watchlist, contributions, log out)?

Or provide a button aside the section titles, that allows the user to go back on top.

Thank you very much, --Daehan (talk) 09:58, 7 August 2020 (UTC)
 * +1. It would be nice, especially if the new top bar is smaller than before as you planned :). Jules* (talk) 12:14, 7 August 2020 (UTC)
 * Hi @Jules*, @Daehan - thank you for the feedback! Adding a persistent header is actually one of the features we are planning on implementing next in the project (will probably begin building within the next 2-3 months). Some mocks on our initial ideas are available on our features page.  In terms of functionality we plan on including the list of features you referred to earlier: logo, search bar, personal links (user, talk, preferences, beta, watchlist, contributions, log out).  We are also considering adding persistent links to edit, talk, and history as well.  Let us know if you have any more thoughts around this.  We're hoping to finalize our ideas and put up a prototype to gather thoughts and feedback within the next month or so as well.   OVasileva (WMF) (talk) 14:41, 11 August 2020 (UTC)
 * great! I think that with those further developments and a bit of polish, new design will be more consistent, and more liked by editors. Kind regards, Jules* (talk) 23:19, 11 August 2020 (UTC)
 * Hello, these are great news! Can't wait for it to happen :) --Daehan (talk) 20:53, 15 August 2020 (UTC)

new header is ugly and creates more empty space!
the new header is ugly! it's smaller, it breaks the harmony of lines, it causes more empty space in the top part of the screen and it's completely unneeded!--Orange-kun (talk) 14:27, 7 August 2020 (UTC)


 * Hey @Orange-kun. The header as is now is just one step towards the look we intend. Later, we will make it sticky (just as requested above), will put more options there, and make aesthetic adjustments. For more details, look at Olga's reply directly above this section. SGrabarczuk (WMF) (talk) 16:02, 11 August 2020 (UTC)
 * @SGrabarczuk (WMF), I've made some remarks on current design and uploaded a screenshot here: please note it! --Orange-kun (talk) 07:28, 12 August 2020 (UTC)

The interface is not practical.
Hello, first of all I would like to thank the developers for the work they have done on this new interface. I contribute and read Wikipedia from a laptop. The screen is not very big. Now that there are the huge borders there is really less room for the content. Maybe the borders are ergonomic on big screens, but on my small screen it's a disaster. I think we should work from Timeless, which is a very ergonomic, beautiful skin, and which adapts very well on small screens (smartphones for example). 3(MG)² (talk) 16:51, 7 August 2020 (UTC)


 * @3(MG)², thank you. In the FAQ, we've explained the reasoning behind the limited content length. What is, according to you, the key advantage of Timeless compared to our change? SGrabarczuk (WMF) (talk) 16:13, 11 August 2020 (UTC)

Improvements
Hi,

I did a tweet with the chapter account to help the people on Twitter

https://twitter.com/Wikimedia_Fr/status/1291679508651704321

I'm personnaly happy of the maximum width. I'm not a huge reader of Wikipedia, but I find articles difficult to read, specially when whe compare Wikipedia to Medium. Since 2014, I'm using a CSS done by Magnus (fr:Utilisateur:Pyb/vector.css). It's basically a 3-column website with the table of content on the left, text in the middle, infobox on the right, and files on the left and right columns. Unfortunately a lot of wikipedians like alterning pictures on the right, on the left... With Vector, you obtain very few words per line!

Thank you for the work, modifying the skin is not an easy task. Pyb (talk) 18:53, 7 August 2020 (UTC)


 * Hey @Pyb thank you so much for spreading information about the project on Twitter, and for your encouraging feedback. It's great to hear that you find the site better to use :) We hope that you will continue following along and giving feedback. Thanks again AHollender (WMF) (talk) 22:38, 13 August 2020 (UTC)

Good intentions, poor execution.
Ok, studies say it's better to have not too large text.

But maybe don't just reduce text width without thinking about the layout at all ?

It looks ok on one of my monitors, but absolutely awful on my laptop. Maybe it would be ok if we still had 4:3 screens ? Well that's not the case.

We already had skins with different width (Timeless, Minerva), they showed perfectly how you could reduce main text and still use space efficiently. Why not take ideas from these ? We know these skins work, they can be a great inspiration for the new version... no need to reinvent the wheel (especially if it's to make it square).

I mean, when the mobile skin looks better than the desktop skin, on desktop, there is an issue


 * No, studies actually say the opposite: it is better to have a large text width. See the comment from User:176.186.245.230 above at quoting Dan Luu. Theo F (talk) 16:35, 8 August 2020 (UTC)


 * Hey the question of that specific Tweet and the study it references is being discussed in another thread. Please see https://www.mediawiki.org/wiki/Talk:Reading/Web/Desktop_Improvements#Comments_on_line_length,_content_separation_and_readability. Regarding the questions around how we might make use of that space, Timeless/Minerva, etc. — we are planning to experiment with similar features. Please see this section for more details: https://www.mediawiki.org/wiki/Reading/Web/Desktop_Improvements/Frequently_asked_questions#But_what_about_all_of_the_white_space!?. Also, if the anonymous contributor who left the initial comment sees this: can you please clarify what you mean when you say "It looks ok on one of my monitors, but absolutely awful on my laptop"? What about it looks aweful?

A way to let users anonymous users maximize the reading window -- a button?
Some users (I am among them) prefer to be able to choose the reading width. As a technical solution, I would like to suggest that an additional button for example with a double arrow ⇔ labelled as “maximize width“, which would toggle modes, the same way that there is a button to collapse/expand the lateral bar.

My use case:

I read wikipedia unlogged on private and public computers. My preferred width appears to be around 1200px, but sometimes different values to fit several windows on the screen. I loved the dynamic width. I could set the old vector style in the preferences, but that is only accessible when logged in. In my case, it means:


 * 1) the annoyance of physically typing in a password every time I want to read a Wikipedia article;
 * 2) the possibility that I occasionally forget to log off from a public computer;
 * 3) possibility that I mistakenly edit a page under a logged account while I intended to edit as IP to avoid linking  some of my interests to my main account;
 * 4) the question of principle that Wikimedia Foundation can now easily track which pages I read (not the same thing as the pages I edit). Maybe the WMF already could infer that using other technical solutions, but now it becomes trivial.

Creating a secondary account for reading does not eliminate the annoyances above (in particular typing a password and losing 30 seconds everytime). Cæruleum (talk) 23:06, 7 August 2020 (UTC)

I followed a tutorial to do a quick hack on CSS with greasemonkey/tampermonkey.

This is a first time for me with CSS/js, please someone experienced help improve it. At the moment the problem is that above a certain threshold in width, it starts teh text below the left bar, which should then be switched to collapsed mode. or it should be the opposite: collapse the lateral bar for small width, expand it above a threshold. Either way, I am not competent.

Plus:
 * works at my place with Firefox 79.0 and Palemoon 28.12
 * a short term solution that requires fewer clicks (just one click to collapse the lateral bar when using at large widths).

Downside
 * needs to be installed on each and every public computer when one reads Wikipedia, including installing an extension
 * on Firefox, requires javascript activated (on Palemoon, Greasemonkey bypasses that somehow).

The commented line about "imeselector" is for when javascript is required. It removes the moving keyboard icon that appears on top right corner of the edition window everytime one types a new line. It moves after 5 seconds of typing something, this is very distracting when javascript is activated. There are probably better ways to have it not move, but I am not competent.

// ==UserScript== // @name       Change_vector_maxwidth // @namespace  example@example.com // @description Changes the width on fr.wikipedia // @include    https://fr.wikipedia.org/* // @version    1 // @grant      none // ==/UserScript==

function addGlobalStyle(css) { var head, style; head = document.getElementsByTagName('head')[0]; if (!head) { return; } style = document.createElement('style'); style.type = 'text/css'; style.innerHTML = css; head.appendChild(style); }

addGlobalStyle('.mw-content-container { max-width: none !important; }'); addGlobalStyle('.mw-workspace-container { max-width: none !important; }'); // addGlobalStyle('.imeselector { display: none !important; }');

The following should press the button so the left bar starts collapsed, which solves the problem where the the text starts below the bar, for large widths. But I cannot make it work. Please someone help.

// https://stackoverflow.com/questions/6337197/greasemonkey-button-click // https://wiki.greasespot.net/Generate_Click_Events var evt = document.createEvent('HTMLEvents'); evt.initEvent('click', true, true); document.getElementById('mw-sidebar-button').dispatchEvent(evt);

Cæruleum (talk) 14:30, 8 August 2020 (UTC)


 * @Cæruleum, we’re working towards the best use case. We are also aware that individual users adjust the layout to their personal needs. Luckily, Wikimedia wikis are massively customizable. There are user gadgets/scripts which change the width already. For instance, see Max-width gadget section. SGrabarczuk (WMF) (talk) 20:08, 11 August 2020 (UTC)
 * As I understand, this solution only work when logged, which was never a problem because several skins are already available. The need I express is for users who read wikipedia unlogged (because of using shared computers, or because the login does not survive closing the browser; see also my discussion above).
 * I am not questioning your new choices, I am instead asking for a help from you competent developers to improve a proposed script that I published above, so that it can be used by me and others who read or edit Wikipedia unlogged, without affecting any of the new defaults.
 * Let me know if a paid bounty would be appropriate, and how I can place such request preferably within the WMF. Cæruleum (talk) 23:03, 11 August 2020 (UTC)

Diff views are extremely narrow
Hi Readers Web team, are there plans around relaxing the width constraints when viewing page diffs? Diffs show side-by-side (i.e. 2-column layout) comparisons of two revisions of a page. The content shown for each revision is the wikitext, and is therefore more verbose than the corresponding content that would be rendered (despite only having about half the horizontal space available). When viewed on a 15-inch screen, the new design reduces the width used for each column in the diff from almost half the screen width to about a quarter of the screen width (see screenshot), making it more difficult to scan (particularly for longer lines that have to wrap) and increases the length of the page (for longer diffs). I don't find that ideal, so I hope we can improve that experience there. Hazard-SJ ( talk ) 03:49, 8 August 2020 (UTC)


 * Thanks for flagging. I've setup T260091 to document the pages where fixed width is problematic. Please feel free to comment there if you find any other pages. Jdlrobson (talk) 22:19, 10 August 2020 (UTC)

Any forthcoming actions following early comments?
People have started to express their feelings about the new layout of the French Wikipedia, but got not much feedback for now. The banner iniviting people to leave their comments here has been quickly removed from articles, while patronizing answers on the French Village Pump explain that problems are mostly with people's mindsets and that the new layout is pretty much okay. Does it mean that basically nothing will be done to improve the situation? — Bob Saint Clar (talk) 07:30, 8 August 2020 (UTC)


 * @Bob Saint Clar, we are collecting data (via API as well) and will make decisions in the near future. It's our intention not to make major decisions directly after the development, based only on the first reactions. SGrabarczuk (WMF) (talk) 16:15, 11 August 2020 (UTC)
 * @SGrabarczuk (WMF): thanks for your answer.
 * I totally understand that you wish to capture a comprehensive feedback from all stakeholders prior to making any kind of decisions: that make sense. In the meantime, is there any page, on Mediawiki or elsewhere, where suggestions and proposals for discussion are logged and investigated, so that we can have an idea of what is being considered exactly, and when any kind of outcome should be expected? — scope, roadmap, timeline, that sort of thing.
 * Bob Saint Clar (talk) 17:00, 11 August 2020 (UTC)
 * You are right, this is exactly our approach.
 * Regarding your question, this very page is the central place for proposals and discussion with the wide editing communities. There's also a Phabricator board with a part of the more technical discussions. If you go through the main navigation tabs and read these pages, you will learn all the crucial information that needs and is possible to be shared now, incl. the scope and sequence of functionalities built and deployed. SGrabarczuk (WMF) (talk) 12:00, 12 August 2020 (UTC)

A mini-minute remark
Of the 3 july changes that affect, as far as I am concerned, the fr.WP ( WP = wikipedia ) and fr.wikt ( wikt = wiktionary ) interfaces (and with my less degree of participation, to eo.WP), much nothing to say, apart "good job ! I appreciate". 1°) I can't say I am much appreciating the collapsible sidebar, since I have been using this functionality with the LeftPaneSwitch gadget for many (?) years, so that I miss it on en.WP. While rereading these words, I notice that this gadget was only present on fr.WP, and not on eo.WP or fr.wikt. So now, the functionality is all there, and on fr.WP, I e havleft the gadget apart. In conclusion : for me; no new functionality, but its presence at more palces ; and more confidence in it, since it's now part of the "system". 2°) The width question : on desktop computer, who is still having a 9 in. wide LCD ?… It's nowadays so easy to zoom the content inside a specific window or to adapt the size of the fonts to the specific use at the peculiar moment… Since I am badly equipped in matter of eyes, it's a thing I permanently do, changing globally the size of the fonts inside a window, an operation which can be done, on my casual OS at home (5 years old since the last major update) as well as with the much newer one at work, with very simple shortcut key commands… So, I am wondering where the problem is, guys ? Those in need just have to learn two new shortcuts and that's fine, most probably. 3°) The logo size and shape… Oh yes, this is a very vital subject… :-))) which I don't care. But I do have a truely definitive real mini-minute remark : I have noticed the disappearance of one crucial functionality : clicking the WP sphere logo was « sending the browser » to the home page of the current project, Wikipedia or Wiktionary. Now, the logo is unresponsive, deaf, insensitive, shamely careless... How-e-ver, since this functionality is the first one in the left column, this means that : if the column is deployed, it's also one click ; but when the column is collapsed, it's now 2, two, TWO ! clics, one to open it, and the second… as usual. Well, I personaly think I can however cope with this newly required tremendous effort of partly doubling the clicks... :-) Conclusion : therefore, thanks to all people who participated to the elaboration then development for these three first modifications. I'll be waiting for the next 10 with no anxiety. Best friendly regards to all readers of this, and to others too. (And I plea guilty for typos, miss-expressions and bad wordings…) --Eric.LEWIN (talk) 07:53, 8 August 2020 (UTC).


 * @Eric.LEWIN, thank you for these kind words! SGrabarczuk (WMF) (talk) 11:46, 12 August 2020 (UTC)

new interface : the main problem is when there is an infobox
Without infobox, the lengths of a line on my screen is ~115 character, and i think that it is good. But when there is an infobox (like at the begining of most article), it is reduce to ~77 and is too short.

But this would be very easy to solve, by putting the infobox in the big empty space at left :

this is the old version : https://i.imgur.com/hGpwlHY.png

this is the new version : https://i.imgur.com/uwDFaof.png

this is my suggestion : https://i.imgur.com/FVN98xx.png

(the dark-mode is the result of 2 addon (dark reader + adjust screen brightness). But it would be easy to make it the dark theme of wikipedia : the brightness of the images is reduce of 20%, the background is 14-14-15 (in RGB) ; the main text is 157-153-147 ; the bleu link is 77-130-180 ; and the title is 177-170-147 .)

--2A01:CB08:AB5:E300:9044:65C:233E:DD66 05:33, 9 August 2020 (UTC)


 * Hey, apologies for the delay in responding. Thank you for taking the time to provide constructive feedback. And we really appreciate you showing your ideas visually, it helps facilitate communication and understanding. I think it's a great point you make — moving infoboxes and/or image templates into the right margin seems like an improvement worth experimenting with, especially given the updated layout. I am not yet sure how this would be possible from a technical perspective but I've added to our list of future considerations. AHollender (WMF) (talk) 13:44, 20 August 2020 (UTC)

The beginning of the line in the page (mainly for wiktionary)
In the old version, there is an bleu line at the left of the article, but not in the new ; and in the new, the text start far from the left limite of the screen. It is mainly a problem for Wiktionary, because there is lot of list, and for the list, we always go the the left, but there is no indicator for where the line start.

We could use this bleu line at the left of the article :

old : https://i.imgur.com/DBp9D1b.png

new : https://i.imgur.com/zeIafni.png

my suggestion : https://i.imgur.com/fMCqj2Y.png

--2A01:CB08:AB5:E300:9044:65C:233E:DD66 06:37, 9 August 2020 (UTC)


 * Hey, thanks for your suggestion. In an attempt to consolidate conversations I'm going to point you to a Phabricator task, on which a similar discussing is happening: https://phabricator.wikimedia.org/T259240. In short I understand the need to have some kind of element that frames the content so it doesn't feel like it's floating. However since there are several other features that we want to work on in that space, we think it makes sense to wait for those features before making any additional changes to the background/border situation. AHollender (WMF) (talk) 18:27, 24 August 2020 (UTC)

What's the plan for Legacy Vector?
What is the the long term plan for "Legacy Vector"? Will it continue to be available as a separate skin, like Monobook is, after the new Vector is deployed as the default skin? /JohanahoJ (talk) 07:59, 9 August 2020 (UTC)


 * Hi @JohanahoJ - that's correct, the Legacy Vector skin version will continue to be available after the switch. OVasileva (WMF) (talk) 14:50, 11 August 2020 (UTC)


 * Ok, thanks! /JohanahoJ (talk) 14:58, 11 August 2020 (UTC)

The width is the same for everyone, but non-Latin wikis look different
There is also a difference in fonts. In firefox settings win10 (font by default) the font size is 16, in the wiki it is already 14 - see where the line ends in the wiki. I put 14-15 in the browser or 13px for the text - a few more words fit into the line. Or I do serif (times new roman) - in another font the text is denser. I take an article in enWP - 150 characters fit in a line, in ruWP - 130. In enWP (and in ruWP with a smaller font size), browsing and reading the text is a little more convenient. In ruWP, the text looks "inflated" and the developers, when forming the length, could only look at sites in English. Non-Latin languages ​​are now less comfortable to read. It is possible that different wikis need different widths or font adjustments for the same number of characters per line. --Sunpriat (talk) 12:50, 9 August 2020 (UTC)


 * @Sunpriat, this is an excellent point. We will definitely look into these settings. SGrabarczuk (WMF) (talk) 16:29, 12 August 2020 (UTC)

The maximum width restriction is a disaster for wide tables and wastes screen space.


I know criticism is not much appreciated, but I am afraid this needs to be said: The maximum width restriction which is planned for Vector 2.0 defeats one of the greatest benefits of the Vector skin and is a disaster for big tables. Not just on Wikipedia, but on countless MediaWiki instances on the Internet. Here are two screen shots of this table in comparison. And here is the Vector 2.0 demo site. The difference is dazzling. Users who actually want a restricted content width already have that option: A “Mobile view” button at the bottom of the page or the browser's so-called reading mode, which all major browsers are equipped with by 2020 and is customizable by the user. I am utterly disappointed about that width restriction. One of the things I appreciated most about Vector will now be destroyed. Also, the change actually does the opposite of improving readability: It forces the user to seek the beginning of lines more often. For this very reason, I read long texts horizontally if I read on a mobile phone.

Suggestions
I sincerely hope that my suggestions will be considered. ---46.114.106.231 12:54, 9 August 2020 (UTC)
 * If this change will actually be made on Wikipedia, please do not make this change a default on MediaWiki, because many MediaWiki instances on the Internet do not allow a user to create an account which would be required to choose MonoBook, which I presume will not be squished like Vector 2.0.
 * Please allow non-account users to choose a skin via a setting that is stored as a browser cookie. The  URL parameter is discarded upon navigation to the next page.


 * I totally agree with you. Lematth88 (talk) 16:12, 9 August 2020 (UTC)
 * wide tables are a disaster on mobile and should be avoid. Pyb (talk) 21:52, 9 August 2020 (UTC)
 * Actually, tables can easily be side-scrolled on mobile phones. Also, us desktop readers do not wish to lose wide tables that look good on a desktop monitor. --79.241.207.77 23:28, 9 August 2020 (UTC)
 * Agreed. Mobile view should be optimized for mobile and desktop view should be optimized for desktop. Otherwise what's the point of keeping them separate. 93.136.89.139 05:26, 14 August 2020 (UTC)

Max-width gadget
Here is a gadget that might be helpful to users who dislike the max width but do not want to opt into the legacy mode. It should give you the best of both worlds and hopefully allow you to see the benefits over time. en:User:Jdlrobson/vector-max-width-toggle.js Jdlrobson (talk) 00:36, 10 August 2020 (UTC)
 * One can also do it similarly with a custom CSS browsing add-on. --79.241.207.77 01:12, 10 August 2020 (UTC)
 * Great! Thank you on behalf of the entire Multiverse, @Jdlrobson :) SGrabarczuk (WMF) (talk) 23:08, 13 August 2020 (UTC)
 * Any plans to roll it out for us 99% of Wikipedia readers who don't have an account? I suggest a link next to the mobile switch. 93.136.89.139 05:25, 14 August 2020 (UTC)

Malfunction
There seems to be a malfunction, the site renders like this: https://wtf.roflcopter.fr/pics/Ekh6WpbZ/bLniiEly.png

Notice the random, non-aligned white and grey areas left and right of the page and overall lack of alignment. M!dgard (talk) 20:32, 10 August 2020 (UTC)


 * Okay, apparently it's intentional. I don't want to just scream "baaad!", and I think a lot about design of websites and web applications these days, creating some myself, so here's a quick critique: https://wtf.roflcopter.fr/pics/lbo0xBlM/lVZUKbid.png M!dgard (talk) 21:03, 10 August 2020 (UTC)


 * Here's a quick mockup that I think fixes a lot of issues: https://wtf.roflcopter.fr/pics/DZcpVMTh/P7fzmmhA.png


 * I haven't touched on the max-width, if that's something you want to keep. M!dgard (talk) 21:40, 10 August 2020 (UTC)
 * , please look carefully at these comments and the proposed fixes that so generously provided. They should all be considered before rolling out these changes to sites like en.WP, where there are many editors who are just as critical but not nearly as helpful. Jonesey95 (talk) 17:20, 13 August 2020 (UTC)
 * @Jonesey95, sure we are! We are watching this page and looking carefully at all comments. As we've outlined on the main page of the project, we are implementing the changes gradually, and adjusting and improving the layout. Our decisions aren't based on talk page feedback only, but also on statistics. Our software is and will be well tested :) SGrabarczuk (WMF) (talk) 22:25, 13 August 2020 (UTC)

max-width CSS rules harm usability
A max-width CSS rule is not relevant for the content of a webpage, because it is possible for users to resize the browser window. On top of this, many browsers offer a "reading mode" that shrinks the text to a small column. Please retract any max-width CSS rules on the content. Calimeroteknik (talk) 20:40, 10 August 2020 (UTC)
 * Yeah. The most used browsers also allow the use of ctrl+plus or ctrl+mouse scroll to zoom in, which gives you fewer characters per line. We who want to read the page in normal width have been forced to resort to unreliable CSS hacks. 93.136.89.139 05:34, 14 August 2020 (UTC)

The new maximum-width rule is making reading experience worst
While I understand the rational behind the maximum line length rule, I found the way it has been implemented (setting up a max-width on the whole article) is making reading experience actually worst than it was before. Some of the issues I noticed / suggestions of improvement:
 * Not properly implemented on large screen with grey areas on the borders => no grey areas
 * Menu of the article (Read, Edit, Search, etc.) has also been reduced causing a strange disruption with the menu in the header => align with header menu on the right
 * Infobox further reduce width of the paragraphs making them very small => Move infobox outside of the max-width limit to the right.
 * Large tables are very difficult to read => allow for large table to extend max-width limitation

pzwsk (talk) 11:25, 11 August 2020 (UTC)

Rollback request
The "content width limit" is very controversial and I believe you have received enough negative feedback already to confirm that it is currently broken. So, please revert this change on the test wikis for the time being. Xhamon (talk) 01:04, 12 August 2020 (UTC)

Peu d'intérêt...
Je suis un utilisateur qui consulte généralement wikipédia sans être connecté (parce que je bouge pas mal, change de PC, ou utilise la navigation privée). Bien qu'ayant remis l'ancienne mise en page en vigueur sur mon compte, je ne comprends vraiment pas l'intérêt de la nouvelle. J'utilise en général des écrans larges où la largeur de texte se trouve maintenant limitée, quand je pouvais auparavant afficher bien plus sans avoir à scroller. Au début, j'ai même pensé que mon navigateur ou mon PC avait planté tellement la qualité de lecture avait baissé.

Pourquoi changer cette interface qui fonctionnait très bien ? Et pourquoi imposer d'autorité ce changement ?

--Sombresprit (talk) 10:09, 12 August 2020 (UTC)


 * D'autant qu'il a toujours été possible de réduire la fenêtre du navigateur pour choisir une largeur de lecture inférieure. Et ça prend beaucoup moins de temps que de se connecter à un compte !! -- Calimeroteknik (talk) 19:02, 18 August 2020 (UTC)

Text width
Please make the text width maximum again. I have a non-magnified 1080p screen and I can only fit seven paragraphs on it.

What the heck is all the white space for anyway? Are you going to run ads? Does somebody think WP will become more relevant if it looks more like Facebook and Twitter? Is WP's readership now intimidated by long, formal texts? Or has Jimbo been bought off by the mouse scroll wheel manufacturers? 93.136.184.51 18:53, 12 August 2020 (UTC)
 * This. The huge columns of whitespace look hideous, such a waste of screen space - almost half the screen is wasted requiring extra vertical scrolling at standard screen resolution. Xaosflux (talk) 04:06, 13 August 2020 (UTC)
 * Ditto. Wide-screen support is still relevant for many readers and editors, including this one. For those looking for workarounds, en:wp:Village_pump_(technical)/Archive_183 has some suggestions. 24.151.56.107 17:35, 13 August 2020 (UTC)


 * If this is what it's gonna look like, then it's not a "desktop improvement". My feedback is: don't do this.--Piramidion (talk) 17:40, 18 August 2020 (UTC)


 * Thank you all for your feedback. We have written up some responses to common questions about the width: https://www.mediawiki.org/wiki/Reading/Web/Desktop_Improvements/Frequently_asked_questions#Why_is_the_width_of_the_content_limited?_Why_is_there_so_much_white_space?. Please understand that we are at the very beginning of this project. There are features coming later on that will make use of the white space on the sides of the screen. AHollender (WMF) (talk) 13:49, 20 August 2020 (UTC)


 * The aloof tone of the answers makes me "wonder" if our feedback "might have been" dismissed out of hand... 93.136.37.250 21:19, 20 August 2020 (UTC)
 * Maybe check your own tone first? —Th e DJ (Not WMF) (talk • contribs) 15:58, 24 August 2020 (UTC)


 * @AHollender (WMF) having to scroll more when there is blank space is not mentioned in that page https://www.mediawiki.org/wiki/Reading/Web/Desktop_Improvements/Frequently_asked_questions#Why_is_the_width_of_the_content_limited?_Why_is_there_so_much_white_space It is easy to see that blank space mechanically pushes content down the page. I believe it is arguable that this is one thing that is wrong with white space. -- Calimeroteknik (talk) 02:33, 22 August 2020 (UTC)

Pourquoi changer ce qui fonctionne.
Cette nouvelle interface n'est pas du tout adaptée à la consultation de contenu sur ordinateur. La moitié de l'écran ne sert à rien, on est bien plus obligés de défiler, et donc de casser sa lecture pour voir la suite du contenu. Les écrans deviennent de plus en plus grand, mais le contenu affiché le devient aussi. La quantité de défilement nécessaire pour naviguer dans les pages les plus longues, avec l'ancienne interface était déjà bien grande, non pas qu'elle gênais, mais on pouvais avoir une bonne vision de la taille des paragraphes, d'un coup d'oeil, on pouvais rapidement voir quelles étaient les sections les plus fournies, avec cette nouvelle interface, la mon index va se fatiguer au vu des défilement à faire, surtout pour les utilisateurs qui n'utilisent pas les ancres dans le sommaire. Si je voulais consulter wikipédia mobile, j'irai sur m.wikipedia.fr, pas sur le site pour ordinateur. je me suis créé un compte uniquement pour revenir à la nouvelle interface, et je pense que je ne suis pas le seul.


 * Exactly, I made this account precisely because I could not stand using the new version of wikipedia. It's so narrow, I hope they will reconsider or to at least give the option to opt out of this new update. --Civicader (talk) 14:42, 15 August 2020 (UTC)


 * On a privacy/anonymity note, staying logged into your account makes it easy for Wikipedia to collect the history of pages you visit. This is indisputable fact. -- Calimeroteknik (talk) 19:00, 18 August 2020 (UTC)

Nouveau style wiki français horrible
Bonjour, le nouveau style du wiki français est vraiment très mauvais. Lorsque l'on lit un article du wiki sur l'écran du PC on a une énormes bande blanche de chaque côté de l'article. Sans déconner on perd pratiquement la moitié de l'espace d'affichage. Le changement est horrible, j'ai l'impression de consulté une version mobile sur un PC. On scroll down beaucoup plus qu'avant aussi, c'est assez pénible. Voilà mon premier problème.

Le deuxième problème c'est que j'ai passé environ 30 minutes à chercher la cause de cette nouvelle mise en page, je pensais que c'était un problème venant de mon PC. A aucun moment, personne n'a pensé a peut être mettre un bandeau d'information qui explique ce qui se passe? La manière de procéder me fait penser qu'on doit accepter le changement et se taire.

Troisième problème, je crois avoir compris que les personnes enregistrés pouvaient modifier l’apparence et revenir à l'ancien format, c'est très bien mais quid de la grande majorité, qui comme moi ne sont pas enregistré, on ne peut pas avoir cette possibilité? Doit-on accepter cette modification et se taire? j'ai juste le sentiment qu'on veut nous forcer à accepter quelque chose et franchement je ne pensais pas que c'était la mentalité de Wikipedia de procéder ainsi.

Pour moi ce changement de largeur rend la lecture des articles vraiment désagréable, pour être vraiment honnête je préfère aller lire les articles en anglais à cause du nouveau design plutôt que des les lires dans ma langue natale.

Mon dernier point, quand est-ce prévu d'avoir au moins une option pour avoir les pages aussi large qu'avant? Merci

voilà my two cents sur ce sujet.

Text columns instead of max-width
Given these clear and blocking regressions of max-width rules, I suggest to instead keep the width, but introduce columns within the text of the articles, like newspapers do. (using media queries)

This would reduce the number of characters per line, but not at the cost of:
 * breaking large tables
 * wasting a lot of screen space
 * forcing people to scroll more

To conclude, the max-width limit brings nothing more than what was possible by resizing the browser window, which takes a split second.

-- Calimeroteknik (talk) 13:33, 20 August 2020 (UTC)


 * @Calimeroteknik thanks for taking the time to write up your idea. We're currently planning to experiment with adding a table of contents and/or page tools within the margins of the article, so that space is most likely going to be used for something. If none of those ideas end up working perhaps we can consider something like you suggest. We have also started discussing some reading accessibility features that would allow people to choose the width of the content. Please do stick around and continue adding valuable ideas like this one! AHollender (WMF) (talk) 13:56, 20 August 2020 (UTC)
 * I wish to make an explicit note here that I believe that any hostility to the changes in this discussion page to come from the regressions, and not from change in itself, or resistance to it, as people pushing that change will feel (consciously or not). From what I see in the workplace, working as an UX designer gets one to develop a specific bias, where any change seems more welcome than keeping the existing, for the sole reason that it is new. By suggesting something entirely new (text columns), I leverage that bias to steer the UX designer's effort towards net improvement of the interface, i.e. without accompanying it with regressions. I believe that the current proposed layout with max-width is a result of yielding to the temptation to break a few things just to fix one downside whose importance got overestimated (especially as it is fixed by a window resize). I mention this out of honesty, and also because I have (possibly unreasonable) hope it could be well-received, and useful. -- Calimeroteknik (talk) 14:37, 20 August 2020 (UTC)

User page of Antandrus
en:User:Antandrus user page looks best on 1024px 1280px width or more? I think our Wikipianist ain‘t going to be happy about the 960px max-width —2003:E5:BF17:7000:E4CD:CE57:753D:EF8F 14:16, 20 August 2020 (UTC)


 * The max width only applies to the content area. The sidebar is 160px width. Last time I checked 1024px is less than 960+160. What am I missing? 157.131.76.233 22:24, 20 August 2020 (UTC)


 * Looking at said user page, I guess (s)he meant 1280px. I corrected it. --46.114.105.71 15:27, 21 August 2020 (UTC)

New content width limit wastes space on a large monitor
For a few days or weeks now, French Wikipedia has started using the new skin. My first reaction to this new theme is that the new content width limit is way too small, and this is especially shocking when using a large screen (I'm using a 27" screen with a resolution of 2560*1440). A rough measure with GIMP shows that the content is now only using 37% of the width of my screen, which looks like a waste of space. (See this comparison: https://twitter.com/s3phyca/status/1296903251753926657 )

I understand while reading Reading/Web/Desktop Improvements/Features/Limiting content width that there's a logic behind this modification. I'm wondering if the data used to come to the conclusion that a width limit is sensible may be old data, predating screens with very wide resolutions? I believe most desktop users have adapted to wider screens that may have seemed way too large at first, but now provide some good usable space to have data on screen.

If a content limit has to be imposed, may I suggest that it be a percentage of the width of the screen and not a fixed value in pixels?

This is only going to get worse with 4K or 8K monitors (although using Hi-DPI might/will mitigate some of this I guess)

Putting aside the number of characters per line (which seems to have some pretty strong sources suggesting a limit for easier readability), I think the real problem here is how much a page looks "empty" by using only a small percentage of the width of a screen. This really feels like a waste of space. I do not have a solution on how to improve that if putting a limitation of characters per line is so important. Maybe using a "columned" view (like newspapers) on very wide screens? Using that "wasted" space for non-text article content? (images, graphs, etc.)

If the character limit per line has to be imposed, then there is a need to find a use for all that space that is going to be freed up. FF7Sephiroth (talk) 21:28, 21 August 2020 (UTC)

I thought about this some more and one more thing is bugging me. This modification takes control away from the user. With the previous, full window width content, the user could choose to have it displayed in a narrower window if they feel that shorter lines is easier for them to read. The width limit now imposes that choice on them.

After thinking about it some more I understand how fewer characters per line makes lines easier to understand, however, most of the times I'm just skimming through articles, or searching through them with Ctrl-F. For that use I do not need the narrower lines, on the contrary I appreciate having more content displayed on one screen for skimming/searching. FF7Sephiroth (talk) 03:41, 23 August 2020 (UTC)

Keep other languages accessible (e.g. like in the mobile skin or in the mobile app)
Hi, I am really excited about this (see my tweet)! One suggestion: We should keep the links to other languages accessible, maybe in the way it's done in the mobile skin or in the mobile app. --Gnom (talk) 14:25, 23 August 2020 (UTC)
 * Have you tried it on a desktop screen yet? 93.136.146.80 07:25, 25 August 2020 (UTC)

What's the workspace area?
Hi. I've read your docs and for now I don't see any purpose for the "workspace" area except to limit line length. Do you plan to add stuff there, like the timeless skin has?--Strainu (talk) 08:21, 24 August 2020 (UTC)

Logo
Please tell me how to include the Chechen logo in the new interface? Screenshot. --Takhirgeran Umar (talk) 11:08, 24 August 2020 (UTC)

Gnome 3
The new changes are from the same people that brought you gnome 3. Your donation money in action. 82.39.171.152 13:19, 25 August 2020 (UTC)
 * Is it actually the same people? Or are you just pointing a general trend among visible UX designers these days (since circa 2011)? -- Calimeroteknik (talk) 17:11, 25 August 2020 (UTC)

Maximum width
Hello, I am coming from the French Wikipedia to support the above messages from other users stating that the set maximum limit to the width of articles is a nonsense: I encourage you to revert back this width limitation, or at least increase the current limit. --LeJC (talk) 16:48, 25 August 2020 (UTC)
 * Dynamic websites are supposed to be able to adapt to any screen, whether they be computer, tablet or smartphone screens. There is now a lot of white space left and right, without any purpose, and more scrolling to reach the content in the lower parts of articles.
 * Giving registered users the option to revert back to the previous display is not an adequate solution for most readers, as they are not registered. Additionally, I guess that this option to use the "old" vector will be removed at some point.