-
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
Grid interactivity: Improve max
attribute logic
#61420
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: +26 B (0%) Total Size: 1.74 MB
ℹ️ View Unchanged
|
Flaky tests detected in 37d0ef3. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/8980246534
|
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.
Thanks for the PR! This is a good little improvement and works well in testing.
max
attribute logicmax
attribute logic
What?
Small fix that I've split out of #59490.
Improves the logic that sets the
max
attribute in the Grid placement input controls. These are currently behind an experimental flag and I doubt they'll ship in WP 6.6.Why?
In a grid that's in manual mode (i.e. it has a column and row count), the user shouldn't be able to set the row or column placement to be such that it would extend past the boundary of the grid.
How?
This makes
max
take into account the Grid block's number of columns/rows and the item's span.Testing Instructions