Classic editor 'more options' disappears at 220% zoom

[johngodley]

Not sure how much of a problem this is, but if you zoom in the classic editor the 'more options' button disappears at a certain point. Here is 200%:

And it disappears at 220%:

The other buttons all wrap round properly as you zoom further

The more button also seems to be 1 pixel too far down vertically, and overlaps the border when you highlight it.

To Reproduce
Steps to reproduce the behavior:

1. Add a classic editor block
2. Zoom the browser window to 220%
3. Note the more options ellipsis menu disappears

Desktop (please complete the following information):
Mac+Chrome

[designsimply]

I tested using WordPress 4.9.8 and Gutenberg 4.4 with Firefox 63.0.1 on macOS 10.13.6 and found that the more menu moves from the top right of the block to below the block at 240% zoom.

^{Seen at https://tan-otter.jurassic.ninja/wp-admin/post.php?post=19&action=edit running WordPress 4.9.8 and Gutenberg 4.4 using Firefox 63.0.1 on macOS 10.13.6.}

I found the same for Chrome 70.0.3538.77 on macOS 10.13.6:

^{Seen at https://tan-otter.jurassic.ninja/wp-admin/post.php?post=19&action=edit running WordPress 4.9.8 and Gutenberg 4.4 using Chrome 70.0.3538.77 on macOS 10.13.6.}

This is the same behavior that we see on mobile (see background explanation at #7256 (comment)).

Perhaps it is still an accessibility issue due to how the placement of the button moves to below the block though?

[johngodley]

Ah yes, I was looking at a long block and didn't notice the menu was at the bottom!

[afercia]

Discussed during today's accessibility bug scrub. Usually, users who need a very high "zoom in" level use screen magnifier software. These tools shouldn't trigger the behavior that moves the More Options button to the bottom.

However, the real a11y issue here is that visual order doesn’t match the DOM order. Worth considering a good percentage of users with accessibility need use their mobile device connected to a keyboard: https://webaim.org/projects/screenreadersurvey7/#mobilekeyboard

Also, this issue seems already covered by #9739 ?

[sabernhardt]

Would it be a good idea to include "maximum-scale=2.0" in the viewport meta tag as a temporary fix, hoping that anyone who needs it larger than 200% uses a screen magnifier as well?

[anevins12]

We need content and functionality to work up to 400% and I don't recommend putting maximum scales on things - sounds like @afercia has found the underlying issue