FocalPointPicker: Deprecate bottom margin#73980
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. |
# Conflicts: # packages/components/CHANGELOG.md
|
Size Change: -222 B (-0.01%) Total Size: 2.58 MB
ℹ️ View Unchanged
|
|
Flaky tests detected in e9e5d36. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/20239284765
|
| * ``` | ||
| */ | ||
| export function FocalPointPicker( { | ||
| __nextHasNoMarginBottom, |
There was a problem hiding this comment.
Should we explicitly ignore it instead of removing? __nextHasNoMarginBottom: _,
I see we use the restProps for the <Container>
juanfra
left a comment
There was a problem hiding this comment.
LGTM. I left one small comment/question.
What?
Part of #73848
Remove the deprecated
__nextHasNoMarginBottomprop fromFocalPointPicker, making the margin-free styles the permanent default.Why?
The soft deprecation was introduced in WP 6.7 and scheduled to be removed in WP 7.0. This removes the prop, completing the deprecation cycle.
How?
__nextHasNoMarginBottomprop fromFocalPointPickerand its types and docs.Testing Instructions
Smoke test the affected components in Storybook and the app.