List of steps to reproduce (step by step, including full links if applicable):
- Go to https://en.wikipedia.org/wiki/American_paddlefish?useskin=vector-2022 (while logged out if necessary)
- Increase your browsers zoom level several times (e.g., with Cmd/Ctrl+Plus)
What happens?:
- Until a certain limit is reached (where the ToC disappears altogether), the ToC dominates most of the screen making the main text pushed off to the right
What should have happened instead?:
- The floating ToC should be more "accommodating" to high zoom levels. It should likely not zoom as much, hide itself sooner, or be able to be disabled altogether as this behavior is inconvenient for some.
Software version (if not a Wikimedia wiki), browser information, screenshots, other information, etc.:
- This is in response to a note brought up on #wikipedia on IRC; the user in question specifically wished for a method of disabling the floating ToC, which doesn't seem currently possible. The portion of interest is as follows, posted here with their permission. (Note the ticket that I linked is incorrect and is for the sticky header, not the floating ToC)
[11:31:47] <peirik> I would like to register a complaint about the new Vector skin: the new, floating, left-aligned table of content panel is ruining my otherwise delicious Wikipedia experience. Please revert this change at your earliest convenience. That is all. Thank you. [11:34:50] <perryprog> peirik, that'd be due to https://phabricator.wikimedia.org/T283505. I had personally assumed there was an option to disable it but I don't see one anywhere... [11:43:18] <peirik> perryprog: Hm, I dont know. I should say I dont mind the sticky header at all. My feud is with the table of contents panel - which is forcing the rest of the (previously centered) page content to the right when a certain zoom level is applied (which I need because my eyes are old and shitty). [11:43:40] <perryprog> Oh that's not good :/ [11:45:28] <perryprog> yeah, I see that same issue. [11:46:52] <peirik> One would think some simple responsive CSS rules could fix it quite easily though :/
Note: Related and possibly duplicated by T306660 and T306904.
