Split this from T313587 about a possibly related sidebar problem

I'm afraid that this is intentional; see e.g. T307901: Add link that allows to hide/show the ToC manually on all screen sizes above 1000px

The mockups and notes in T307901 don't seem to say that a new sidebar behavior (stretch entire sidebar to full width) is expected?

Sorry, but closing this as "by design" is unacceptable if Vector-2022 is to become the default for new users. On Windows, docking to the left or right, so that the user can see two portrait windows side-by-side, was promoted as a common practice for those of us who suffered Windows 8, and I can't imagine I'm the only one who still has it as part of the normal workflow. Now, on most screens with an HD-like aspect ratio (somewhat old 1920x1080, or today's 2736x1824 at 175% OS scaling), docking to one side results in [https://1drv.ms/u/s!AtuCZY0YF4hGpK07b9IGdnUnGtV3_Q this] view of the main page. Is that the initial impression we want to give? I'm going to have to revert to Vector-2010 until this problem is addressed.

@DavidBrooks did you read the FAQ I linked to above ? It explains how the existing design is an interim solution.

@Jdlrobson My apologies; I had not realized the implication of the linked entry (in my defense, I was too much triggered by the word "expected", but that's my fault not yours). I'll get off my high horse and temporarily go back to classic Vector. Is there a task I can track that will tell me when the better solution is rolled out?

No problem! To be fair on you, my comment was briefer than it should have been. There's quite a few moving parts for this work, but currently subscribing to T302073 is the best way to keep track of where we are with the new pop out menu.

That's fine. We can resolve/decline this when the new version of the main menu dropdown is in place.

This is fixed for logged-in users but still broken for logged-out users. It is disorienting and pushes the whole page down roughly one screen-length.

We are completely the roll out of page tool to logged in users this week: https://phabricator.wikimedia.org/T328692. After that my understanding is we will gradually roll this feature out to anonymous users on non-English Wikipedia wikis. This however is dependent on talking to and identifying which communities are happy to trial the change. We don't tend to deploy to English Wikipedia for anonymous users for new features, due to the fact issues are more difficult to correct given the importance of page caching for anons.

Hi @Jdlrobson! I don't believe this is related to the roll-out of page tools.

Here is what it looks like to open the main menu (at just under 1000px, on FF/Mac):

1. When logged in, working as expected:

2. When logged out, this is a bug:

@Sj the dropdown behavior is tied to page tools which is currently only enabled for logged in users. You can force it on using https://en.wikipedia.org/w/index.php?title=Main_Page&vectorpagetools=1 in an incognito window to get a sneak preview of how that works.

Ah I see, thank you.

I think this particular regression is serious enough that at least the menu fix should be applied on all wikis.
The Main Menu has core links that every reader should have easy access to (help, RC, random, learning to edit, &c), it isn't reasonable to say "don't use the main menu until this is fixed"

This is still happening for a few pixels of width right around the scaled equivalent of 1000px, at some browser zoom levels (900px @ 90%, 1100 px @ 110%, 1250px @ 125%, &c. ... but not at 50% or 100%).

To experience this, just increase your browser zoom to 110% and size the browser to 1100px and shift it slightly back and forth. (you can also see the larger than usual flicker as you adjust window size across the transition, which is how I noticed this; pausing at the flicker leaves you in this state.)

It affects both the main menu and the tools menu, so if both are open, one appears above the page title and one appears just below it:

This happens both when logged in and when logged out. (FF and Chrome on MacOS).

@Jdlrobson should this be reopened or is this a separate issue?

Update: if I start with the menus closed and adjust the window width to this uncanny region, the CSS ends up in this weird state, with squashed topbar and no icon for the TOC:
{F37157748}

@stjn Can you replicate this in safe mode? I notice you have some rules here https://en.wikipedia.org/wiki/User:Sj/vector-2022.css which might be influencing this. I wasn't able to replicate the font-size / screen resolution combos that you shared.

I'm aware of T341580 which might be the issue you are seeing?

Thanks, that's the bug I was looking for. Yes, I can make it happen logged-out also, on a different browser.

(Not @Sj) In the future, please do not merge the tasks like that, as that subscribed me to something I do not really have any interest in :-)

Sorry about that @stjn but glad to hear from you. I will be more careful in future. :-)