-
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
Zoom Out breaks sticky positioned elements #64117
Comments
Do we want to respect position sticky in this view? I am afraid it will make it very dubious when trying to assemble patterns. cc @WordPress/gutenberg-design |
What works better in practice? If disabling it works well enough, that can be fine to do. Though it's reasonable to think about position: fixed being a thing that can exist in the future, in that same interface. |
I am bit more strong on this and think we should close this as wontfix because enabling absolute/fixed position in zoom out will obscure via z-index the assembly of patterns / sections which this view is meant for. |
This is also one of those things where we can start with one thing, and then can explore if need be alternatives as we get a feel for edgecases. |
I reckon it's okay to ignore position in this mode for now. That said, if zoom ever becomes a dedicated view option that users can toggle regardless of mode then we may need to add support. |
I agree with the others. Sticky elements will obfuscate pattern selection quite a bit. Let’s close this for now and perhaps revisit when zoom out is in a more stable position. |
Description
In the zoomed out view sticky positioning ceases to work. It’s due to the
transform
applied to thehtml
element in the iframe.Possible fixes
iframe
instead of thehtml
element (etc. Refactor Zoom Out to scaleiframe
#63390)html
andbody
to beheight: 100%
body
tooverflow: auto
html
, etc.)Step-by-step reproduction instructions
Here’s a sticky block you can paste into the editor:
Screenshots, screen recording, code snippet
zoom-out-v-sticky.mp4
Environment info
WP 6.5.2 / Gutenberg trunk
Chrome / MacOS
Please confirm that you have searched existing issues in the repo.
Please confirm that you have tested with all plugins deactivated except Gutenberg.
The text was updated successfully, but these errors were encountered: