@Jdlrobson @Jdrewniak I'd like to use this task to articulate any drawbacks we see to adding initial-scale=1 to Vector 2022. As far as I can tell it's a big usability improvement.

This behavior is an obvious usability improvement but is currently intentional as several editors have explicitly requested it. Many editors vocally detest responsive sites. You may remember this came up recently with iPad users where users complained that the table of contents was collapsed (T306910).

We already have a solution for this (it's a one line change if we ignore the existing issues with large images and tables). The solution here is to make the responsive preference in Special:Preferences apply to Vector 2022. That would turn this behavior on by default and those editors that dislike it would be able to opt out ( anonymous users would have to request desktop site). That change is trivial but the social implications are quite high and I would recommend the English Wikipedia running an RFC on it before we did that there. This work is tracked in T106463

Is there a way to add this individually with userJS/CSS? (or Greasemonkey/etc?) I think it might be the missing ingredient to make my mobile reading and editing a joy with Vector-2022, and would love to test it out!

@Quiddity

importScript('User:Jdlrobson/responsiveVector2022.js')

Edit (if not using enwiki):

importScriptURI('https://en.wikipedia.org/wiki/User:Jdlrobson/responsiveVector2022.js?action=raw&ctype=text/javascript')

Should I drop comments on your talk page about papercuts with that (images and tables generally already having their own tasks)? I've already bumped into a few things that could use adjustment that I think should be pretty easy to take care of. (And if not, could be considered actionables before any potential deployment.)

@Izno is that a question for me? Regarding images and tables - yes the plan is to fix them inside Vector itself (we're looking at images over the next 2 weeks).

There are no plans to make Vector responsive this year (by that I mean adding a meta[viewport] tag to the HTML of desktop) as we don't have capacity to handle the backlash I expect we'd get from certain community members (there are lots of community members who don't seem to want a responsive desktop skin) so for now but feel free to suggest improvements to [[User:Jdlrobson/responsiveVector2022.js]] or turn it into a gadget. Improvements to Vector itself to better handle content responsively (e.g. when you resize the browser) are always appreciated.

Yes, I'm asking where is best to suggest improvements to the script and/or skin based on use of the script. :)

Talk page is fine. We can create phabricator tickets for anything that comes out of that discussion.

Problem with long titles: