@AHollender (WMF): Is there some reason why not to do the screenwidth toggleable in same way than the sidebar is collapsible? In that way you could dart most of the critic and also you could get actual data how many users are using narrower or wider screens. It would be also an useful feature.
Second question is that if you arent doing it by yourself then would it be possible that somebody else would do it submit a patch?
Hey @Zache — I agree that we should offer the ability for people to toggle the content width between a more narrow and more wide option. In terms of how we might achieve that I think there are at least two ways:
1) a bit further along in the project our team is going to look specifically at the use case of people with large screens. The same way that we want people with small screens to have a good experience, we also want people with large screens to have a good experience. There's a chance that at that time we would work on the type of toggle you mentioned
2) a developer could certainly build this type of functionality as a gadget. I think it would be great if this happened sooner rather than later because it would help us understand how many people would want/use this kind of thing, and could help with our own prioritization process. And even if we didn't get around to building a more "official" version of the feature it would at least be there for people who know how to use gadgets.
Also, to keep in mind, we are still developing an improved table of contents experience and there's a chance that it will sit to the left of the article (on LTR languages). So from that perspective it might make sense to wait a bit longer before developing a gadget to toggle the content width.
Thanks for the answer, I actually made an added an gadget it to fiwiki's settings (Pienoisohjelma lisää sivun yläreunaan napin jolla uuden Vector-käyttöliittymän version saa koko näytön levyiseksi) after I readed discussion in fiwiki which included complains on the width limitation.
However, problem with user scripts and gadgets is that the gadgets javascript is executed after the page is loaded so there will be a visible "flicker" if the content is resized by the gadget. This will limit how well "toggle" can work in terms of user experience. It would be a lot better for the if the wanted state would be stored as a setting and it would be already in CSS when page is generated.
@Zache oh wow that's so cool. I've just tried it out. I understand your issue with the "flicker". I pinged @Jdlrobson who might be able to advise you on how to fix that.
I was able to least partially fix the flicker. I splitted it two different gadgets. One for toggle button and clicks. Second gadget is CSS-only and for initial "wide state" when page is loaded. The button will resize the page, but also toggle the CSS-gadget on/off.
Btw, do we have any stats how many users are using the new Vector in finnish Wikipedia? (or is there any method how to get weekly stats etc)
@Zache awesome — glad you have been able to make progress on that. Regarding the number of people using new Vector on Finnish Wikipedia, I've pinged @OVasileva (WMF) and @SGrabarczuk (WMF) who might be able to provide that information.
