Normalize block gap values in layout - #81460
Conversation
ramonjd
left a comment
There was a problem hiding this comment.
This is working well for me. No blockers aside from the linting/backport
|
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. |
andrewserong
left a comment
There was a problem hiding this comment.
This is working well for me. No blockers aside from the linting/backport
Same here. Good idea adding this hardening!
|
Flaky tests detected in d385ee6. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/31562336544 should update the URL from the last navigation if only varies in the URL fragment in
|
What?
Closes #52099.
A little overdue cleanup to ensure block gap values are either strings or numeric zero (if gap is an array, the array should also have only those values). This will hopefully prevent PHP warnings or fatals from incorrect values.
Testing Instructions
px,vw... and numeric0should all work correctly in the front end.Use of AI Tools
Used codex/gpt 5.6 sol