-
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
GradientPicker: Hard deprecate outer margins #58701
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 SVNIf you're a Core Committer, use this list when committing to
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: -180 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
__nextHasNoMargin
on GradientPicker to the default behavior.Why?
The deprecation grace period has elapsed.
Testing Instructions
In the Storybook for GradientPicker, turn on the margin checker tool in the toolbar. The margin-free styles should now be the default, and the
__nextHasNoMargin
prop should not be listed in the props table.✅ There is one direct usage of GradientPicker in the Gutenberg app, and it's already using it in margin-free mode.
✅ All internal components that use GradientPicker under the hood are already using it in margin-free mode.
✍️ Dev Note
See Dev Note for #58699.