-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
POC: Try fixing Safari top toolbar issue. #53665
Conversation
Size Change: -1 B (0%) Total Size: 1.51 MB
ℹ️ View Unchanged
|
Flaky tests detected in 1609f79. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/5864991667
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change breaks how the inspector scrolls. It does not scroll independently anymore.
Ack, that's disappointing, but I figured there was a good reason for the value. I'll have to debug further, notably around why it gets cropped off not always, but only when the viewport is small, but would appreciate additional brains on this 🙏 |
Closing in favor of #53688 |
What?
Proof of concept: do not merge yet.
Work in progress to fix #53495.
Why?
In Safari, for whatever reason when the viewport gets reduced in height,
.interface-interface-skeleton__content
gets "Scroll" applied, which crops off the top toolbar which is pushed up to cover the main bar at the top:This is more easily shown in this GIF of the inspector, showing the "Scroll" property appearing when resizing the window:
So far this PR "fixes" the issue by removing the overflow value. However there's a great deal of prior comments around why that overflow property was added in the first place, so this needs a bit further debugging.
How?
It appears that the overflow as applied to the main viewport causes the cropping of the top toolbar.
Overflow of course makes the various containers scroll, this is valid enough, and a better fix might be to move where the toolbar lives so that it does not get cropped by the container that has overflow applied. However the position in the DOM is also delicate territory, so any testing, especially of the mobile use case, would be valuable. If the following instructions are obsolete, this PR can in fact land:
Testing Instructions
Observe how in trunk, the toolbar disappears, in this PR it stays.