-
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
FontSizePicker: Hard deprecate bottom margin #58702
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 Core SVNCore Committers: Use this line as a base for the props when committing in SVN:
GitHub Merge commitsIf 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: -170 B (0%) Total Size: 1.69 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.
🚀
Part of #39358
What?
Promotes
__nextHasNoMarginBottom
on FontSizePicker to the default behavior.Why?
The deprecation grace period has elapsed.
Testing Instructions
In the Storybook for FontSizePicker, turn on the margin checker tool in the toolbar. The margin-free styles should now be the default, and the
__nextHasNoMarginBottom
prop should not be listed in the props table.✅ The wrapped FontSizePicker component exported from
@wordpress/block-editor
followed the same deprecation schedule as the canonical FontSizePicker component.✅ Other usages in the Gutenberg app already are in margin-free mode.
✅ There are no internal components that use FontSizePicker under the hood.
✍️ Dev Note
See Dev Note for #58699.