-
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
BoxControl: Passive deprecate onMouseOver
/onMouseOut
#67332
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: -2 B (0%) Total Size: 1.83 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 👍
Testing instructions worked well, and I confirm the sole use case was in DimensionsPanel
.
🚀
…7332) * BoxControl: Passive deprecate `onMouseOver`/`onMouseOut` * Fix usage in DimensionsPanel * Add changelog Co-authored-by: mirka <[email protected]> Co-authored-by: tyxla <[email protected]>
* BoxControl: Passive deprecate `onMouseOver`/`onMouseOut` * Fix usage in DimensionsPanel * Add changelog Co-authored-by: mirka <[email protected]> Co-authored-by: tyxla <[email protected]>
Follow-up to #67284 (comment)
What?
Passive deprecates (#61099) the
onMouseOver
/onMouseOut
props on BoxControl. These props should be passed from theinputProps
prop instead.Why?
This is an administrative change to streamline the props so they make more sense.
It is misleading and unnecessary for the
onMouseOver
/onMouseOut
props to be exposed at the root level on BoxControl. They can be passed through from theinputProps
prop, and that is where they are ultimately passed anyway.Testing Instructions
dimensions-panel.js
file, override theshowSpacingPresetsControl
variable tofalse
.trunk
.Technically I think the Padding control should also be working like this, but it doesn't quite work as expected for me in trunk either. Possibly related to #63191. It works once you commit a padding value by hitting the Enter key.