Unset grid span defaults with viewport states enabled#78709
Conversation
d3a395c to
76949fd
Compare
|
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: +34 B (0%) Total Size: 8.18 MB 📦 View Changed
ℹ️ View Unchanged
|
|
Flaky tests detected in 76949fd. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/26492888361
|
andrewserong
left a comment
There was a problem hiding this comment.
Nice polish, this is testing well for me!
In the following screengrab, I've set desktop to 2/1 for a paragraph, on tablet I've explicitly set it to span 1 column, and mobile it's left blank. All feel clear to me:
2026-05-28.14.58.02.mp4
🚀
Co-authored-by: tellthemachines <isabel_brison@git.wordpress.org> Co-authored-by: andrewserong <andrewserong@git.wordpress.org>
|
I just cherry-picked this PR to the release/23.3 branch to get it included in the next release: def6279 |

What?
Follow-up from #78543.
When a column or row span is set on a grid child, and then a non-default viewport state is toggled, the span controls appear with their default value of "1", when in fact they have no viewport value set. If we want to set that value explicitly to 1, we're forced to change the value to something else and then back to 1 for it to apply.
This PR fixes the issue by removing those inaccurate defaults when viewport states are enabled.
Testing Instructions