-
Notifications
You must be signed in to change notification settings - Fork 21
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
Fixes for breaking changes from Gutenberg 11.4 #30
Conversation
This better accommodates the change in Gutenberg that causes all blocks that support `experimentalLayout` (the Group block) to get the `wp-container-[hash]` class added during rendering. See Automattic/themes#4459
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.
LGTM 👍🏻
great job on the docs, and thanks for the early heads up 👍🏻
source/wp-content/themes/wporg-news-2021/sass/blocks/_post-title.scss
Outdated
Show resolved
Hide resolved
source/wp-content/themes/wporg-news-2021/sass/post/_header.scss
Outdated
Show resolved
Hide resolved
@iandunn Do you want to address the global header margins in the PR, or in a separate one? Here's what it's looking like right now: |
I'll take care of it in #28 , I've got it mostly working locally, but am playing around with a few approaches |
Our theme had some alignment styles from Blockbase that didn't play well with changes introduced in Gutenberg 11.4. I went and found the commit where Blockbase was fixed to accommodate those changes and brought it over, and it seems to mostly fix the problem described in #29.
This is still a bit of a work-in-progress as I try to figure out if I can avoid introducing more
!important
clauses to the stylesheet, but I wanted to get your eyes on this @iandunn because it also appears to affect the global header (currently it's getting some margin added on the sides instead of being full-width).