You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How long would the "old format" be supported? Does leaving older themes alone make sense?
Does changing the configuration change the user experience in any way?
This would have to be a post-6.1 change right?
If the above checks out I suggest instead we target specific themes (Block Canvas for sure, Blockbase, and perhaps any theme made in the last couple of months).
I think it's good practice for us to keep all our block themes up to date, but I realise this is a lot of maintenance, especially with the speed of Gutenberg changes. Updating Block Canvas as a priority sounds good to me.
I don't believe the configuration changes the end-user experience, and as far as I know it's backward compatible.
Yes, this would need to be post-6.1 (this change was in GB 14).
I am working on my posts page. Using 6.2 WordPress. There is a gap between the post title and the post excerpt that seems to come from body .is-layout-constrained > * + * {} and/or body .is-layout-constrained > * {}. They are causing margin-block-start and margin-block-end declarations,
Where and how can I turn off these horrid declarations?
They are set at 24px and they are ugly.
Quick summary
Now that WordPress/gutenberg#42763 has been merged, we should consider updating all block themes to use the new layout setting.
The templates should be updated to use the new layout setting for container blocks:
"layout":{"type":"constrained"}
: Inner blocks have wide and full width options. Replaceslayout":{"inherit":true}
"layout":{"type":"default"}:
inner blocks do not have wide and full width options. Replaceslayout":{"inherit":false}
I don't believe this is a breaking change, but it would be nice to use the correct, up-to-date settings.
Steps to reproduce
n/a
What you expected to happen
n/a
What actually happened
n/a
Browser
No response
Context
No response
Platform (Simple, Atomic, or both?)
No response
Other notes
No response
Reproducibility
Consistent
Severity
No response
Available workarounds?
No response
Workaround details
No response
The text was updated successfully, but these errors were encountered: