Select: Fix disabled cursor styles#78112
Merged
Merged
Conversation
|
Size Change: 0 B Total Size: 7.92 MB ℹ️ View Unchanged
|
mirka
changed the title
|
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. |
|
Flaky tests detected in 5c384d4. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/25582970891
|
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What?
Fixes cursor styles for disabled
@wordpress/uiselect controls so disabled triggers and popup items do not use the interactive control cursor.Also fixes it for disabled items in
Autocomplete.Why?
Disabled controls should not visually imply that they can be interacted with.
How?
Applies
cursor: var(--wpds-cursor-control)only when the select trigger or popup item does not havedata-disabled.Testing Instructions
@wordpress/ui.Design System/Components/Form/Primitives/Select.Disabledstory and confirm the disabled trigger does not show the interactive control cursor.With Disabled Itemstory, open the select, and confirm the disabled item does not show the interactive control cursor while enabled items still do.