BoxControl: Passive deprecate onMouseOver/onMouseOut
#67332
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mirka
added
[Type] Code Quality
|
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
|
tyxla
approved these changes
Nov 28, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Follow-up to #67284 (comment)
What?
Passive deprecates (#61099) the
onMouseOver/onMouseOutprops on BoxControl. These props should be passed from theinputPropsprop instead.Why?
This is an administrative change to streamline the props so they make more sense.
It is misleading and unnecessary for the
onMouseOver/onMouseOutprops to be exposed at the root level on BoxControl. They can be passed through from theinputPropsprop, and that is where they are ultimately passed anyway.Testing Instructions
dimensions-panel.jsfile, override theshowSpacingPresetsControlvariable 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.