-
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
FocalPointPicker: Default to new 40px size #64456
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: -25 B (0%) Total Size: 1.77 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.
LGTM 👍 Thanks!
Feels good to see this kind of PRs finally landing 🥳 |
Part of #46741, #63871
What?
Default the FocalPointPicker to the new 40px size.
Why?
I think this was one of those components where we didn't need to have a transitional period with the
__next40pxDefaultSize
prop. It is a compound component, similar to ColorPicker or TimePicker, which won't cause serious breakage due to the input fields being upsized. The component won't be used in a context where upsizing the inputs would cause overflows, for example.How?
Remove the prop and all it's now-unnecessary usage in the codebase. (All usage in the app was already switched to the 40px size.)
Testing Instructions
Usages of FocalPointPicker should now default to the larger size. Also, having the
__next40pxDefaultSize
prop should not cause TypeScript compilation to fail (only marked as deprecated).