Try removing top and left grid drag handles in stable (auto) mode #73864
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tellthemachines
added
[Type] Enhancement
|
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. |
Contributor
Author
Just tried this and pushed the result so folks can test! Having the drag handles feels less frustrating; on the other hand the results of dragging can be unexpected, as blocks grow down almost invisibly (because new rows have no intrinsic height) or they jump to the next row when being expanded to the left: dragging-inside-grid.mp4This may be why we considered disabling those drag handles in the first place 😅 Would love some opinions on this! |
|
Size Change: +30 B (0%) Total Size: 2.57 MB
ℹ️ View Unchanged
|
ramonjd
approved these changes
Dec 10, 2025
Member
ramonjd
left a comment
ramonjd
left a comment
There was a problem hiding this comment.
Just to check if I'm reading this correctly - blocks not in the extreme right or bottom of a grid shouldn't have have left or top drag handlers anymore.
I'm seeing this (on bottom top and middle rows of my grid)
| Before | After |
|---|---|
 |
 |
 |
 |
 |
 |
I checked with the experiment on and off, and saw the same.
LGTM
Contributor
Author
Yes! I think that whether we ultimately decide to keep the handles for bottom/right blocks or not, this PR improves on trunk so might be worth merging if there's no strong opposition to it 😄 |
Contributor
No strong opposition to it from me! 😄 I like the idea of (at some point) bringing them back if there's a way to actually rearrange the blocks at the same time. Until that point, I agree with the premise of this change, that hiding the drag handles will help reduce confusion, so it seems the pragmatic change to me 👍 |
Contributor
Author
|
Thanks for the reviews folks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What?
Closes #63966
If the grid experiment is disabled, or when enabled, if the Grid block is in Auto mode, top and left drag handles for grid items shouldn't show.
The downside to this is, of course, that it now becomes impossible to resize by dragging a block in the bottom right hand corner of a grid, because it won't have any drag handles:
Blocks on the bottom and right sides will be limited in their draggability. Other blocks should still be draggable towards bottom and right:
I suppose it would be possible to add top/left drag handles only when blocks are on the bottom or right sides. I might experiment with that as I feel that not being able to drag at all is suboptimal.
Testing Instructions