-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Grid layout: Try moving resizer popover slot to fix display on mobile #63920
Grid layout: Try moving resizer popover slot to fix display on mobile #63920
Conversation
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.
To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Size Change: -4 B (0%) Total Size: 1.76 MB
ℹ️ View Unchanged
|
Just doing a flyby test. Looks pretty good! Kapture.2024-07-25.at.16.23.17.mp4There's a comment about this slot that it's meant for the inline rich text, popover - but that was a while back so maybe not relevant. |
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.
Good catch. GridItemResizer
and GridVisualizer
should use the same slot 👍
Thanks for confirming, Rob! |
What?
Part of #57478, might fix #63275
Similar to #63389, try updating the Grid resizer to use a different popover slot, that is after the editor canvas.
Why?
I noticed that as of #63389, the grid visualizer doesn't erroneously appear on mobile when the list view is open. It seems that if we update the resizer to use the same popover slot, then it'll also no longer appear when the list view is open and a child of a grid block is selected.
Note: I'm not too sure if there are any downsides to this approach, so pinging @noisysocks for a second opinion here 🙂
How?
"__unstable-block-tools-after"
slot.children
toBlockTools
hereTesting Instructions
trunk
Testing Instructions for Keyboard
Screenshots or screencast