-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Post editor: increase specificity bottom padding #63288
Conversation
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: +10 B (0%) Total Size: 1.76 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.
Thanks for the fix! It appears to work correctly in all scenarios.
- Classic Theme, Post Editor is iframed:
- Classic Theme, Post Editor is not iframed:
- Block Theme, Post Editor is iframed,
useRootPaddingAwareAlignments
istrue
:
- Block Theme, Post Editor is iframed,
useRootPaddingAwareAlignments
isfalse
:
The following two points cannot be tested in the usual way on the Gutenberg plugin. This is because if the Gutenberg plugin is enabled and the theme is a block, the editor will always be iframed.
I temporarily removed the || ( isGutenbergPlugin && isBlockBasedTheme )
condition and tested a block theme, non-iframe editor.
- Block Theme, Post Editor is not iframed,
useRootPaddingAwareAlignments
istrue
:
- Block Theme, Post Editor is not iframed,
useRootPaddingAwareAlignments
isfalse
:
Another issue I noticed while testing this PR is that when the editor is not iframed because a meta box is present, the bottom padding is not applied:
On the other hand, when the meta box is not present but a v2 or lower block is registered and the editor is not iframed, the bottom padding is applied.
However, I found that this issue also occurs in WP6.5, so I don't think it's a blocker for this PR.
Co-authored-by: ellatrix <ellatrix@git.wordpress.org> Co-authored-by: t-hamano <wildworks@git.wordpress.org> Co-authored-by: talldan <talldanwp@git.wordpress.org>
I just cherry-picked this PR to the wp/6.6 branch to get it included in the next release: 9baef2c |
Co-authored-by: ellatrix <ellatrix@git.wordpress.org> Co-authored-by: t-hamano <wildworks@git.wordpress.org> Co-authored-by: talldan <talldanwp@git.wordpress.org>
Co-authored-by: ellatrix <ellatrix@git.wordpress.org> Co-authored-by: t-hamano <wildworks@git.wordpress.org> Co-authored-by: talldan <talldanwp@git.wordpress.org>
What?
Increases the specificity of the body bottom padding to override any padding set by global styles.
Why?
Fixes #63278.
How?
Set to 0-1-0. Alternatively we could use
!important
, but I guess we better avoid that if we know the specificity needed.Testing Instructions
See #63278.
Testing Instructions for Keyboard
Screenshots or screencast