I'm not 100% sure this is exclusively happening on RTL wikis. I will check.

Happens in enwiki as well:

But it has a scroll in enwiki, not in fawiki...

What screen resolution is that and what device? Good news is that it should be fixed in T264206 in current deploy.

In T267325#6606792, @Jdlrobson wrote:

What screen resolution is that and what device? Good news is that it should be fixed in T264206 in current deploy.

The user says it's a desktop (laptop) with resolution of 1024x768px

Okay thanks for clarifying. Yes this will be improved in next deploy but not fixed so we need to do something here.

We'll need to update the CSS. We need to disable the CSS Janus rtl flipping that occurs here.

Note this impacts the newly proposed anguage switcher too.

This happens because on legacy Vector, the search box provides enough space for the more menu underneath it:

current more menu (legacy Vector)	current more menu (legacy Vector)

In modern Vector, without the extra space provided by the search-box, the text is very likely to fall off the edge of the page. I think this could be an issue at smaller resolutions for many languages with long words, leading to horizontal scrolling.

Instead of adding the /* @noflip */ comment, I think what we can do is right-align the menu instead:

end-aligned menu RTL	end-aligned menu LTR

I tried the approach of right-aligning the menu, but then I realized it affects legacy Vector too. The only way it wouldn't look broken in legacy is if we right align the text inside the menu as well:

I’m not sure if design-wise this is acceptable but it would avoid conditional code for modern & legacy Vector.

It's possible I might have fixed this accidentally in https://gerrit.wikimedia.org/r/c/mediawiki/skins/Vector/+/631552

@Jdlrobson indeed! The 500px patch has the following effect on the more menu.

Modern Vector	Legacy Vector

( It should also right-align the text in the menu).

@Jdlrobson I'm curious how complicated it would be make this change to the menu modern-Vector specific?

Also just want to loop @alexhollender in on this conversation.

In T267325#6738368, @Jdrewniak wrote:

I tried the approach of right-aligning the menu, but then I realized it affects legacy Vector too. The only way it wouldn't look broken in legacy is if we right align the text inside the menu as well:

I’m not sure if design-wise this is acceptable but it would avoid conditional code for modern & legacy Vector.

I'd strongly pledge against right-aligning the menu items themselves. This might even affect folks with readability impairments (need to find the article in my bookmarks talking about this, but this solution would also decrease usability.

This is fixed at lower resolutions e.g < 768px, but not at larger resolutions, so I think we should need to drop a media query somewhere.

Change 658267 had a related patch set uploaded (by Jdrewniak; owner: Jdrewniak):
[mediawiki/skins/Vector@master] Align the Vcetor menu dropdown list to the end of the "more" button.

https://gerrit.wikimedia.org/r/658267

@Jdlrobson @Jdrewniak @Volker_E this is what I'm currently seeing in production, which looks good to me:

legacy vector	vector

are there any remaining issues here?

Change 658267 merged by jenkins-bot:
[mediawiki/skins/Vector@master] Align the menu dropdown list to the end of the "more" button.

https://gerrit.wikimedia.org/r/658267

@alexhollender the issue the patch above addressed was at larger resolutions, e.g.

Test Result - Beta

Status: ✅ PASS
Environment: beta
OS: macOS Big Sur
Browser: Chrome
Device: MBP
Emulated Device: NA

Test Artifact(s):

The more menu is clipped when the margin is absent in our sites on RTL

As you can see in this screenshot with margins, the more menu in the top left corner is not aligned correctly with the more menu

When the screen resolution shrinks to around 1024x this results in the more menu disappearing off the page

✅ AC1: The left side of the more menu should be aligned to the more button on RTL wikis

@Edtadros I think this change may not have made the train last week. Looking at it now, I think those issues have been resolved.