-
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
Layout: Add not .alignfull rule from root CSS PR #42614
Layout: Add not .alignfull rule from root CSS PR #42614
Conversation
Size Change: +6 B (0%) Total Size: 1.25 MB
ℹ️ View Unchanged
|
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.
Tested with Twenty Twenty Two by following the steps outlined in #42604 and can confirm this fixes the issue for fullwidth blocks in both the front end and the editor (provided the theme styles define negative margins for the block).
Added the Needs Dev Note label in case this needs a dev note (either individual or as part of a "misc" dev note) for WP 6.1 release. |
What?
As reported in #42604, Gutenberg 13.7 was released but didn't include the fix for full width alignment introduced in #42085 (that PR is slated for 13.8).
This PR attempts to grab a couple of the fixes for the full width alignment, and targets the
release/13.7
branch. This PR exists in case it's desired to push a patch / point release without having to include or cherry pick all of #42085.Why?
Due to the issue in #42604 causing issues for TwentyTwentyTwo (or themes with their own custom negative margin rules for full width alignment blocks) it could be worth a higher priority fix than waiting for 13.8.
How?
Add the
:not(.alignfull)
pseudo class rule to the content size and flow layouts so that the!important
margin-left and margin-right rules aren't applied to full width alignment blocks.Testing Instructions
Follow the testing steps in #42604 and see if this PR resolves the issue. Is it enough as a shorter-term fix, or do we need to revisit the specificity of the selectors?
Screenshots or screencast