UI Button: Fix disabled cursor style#78479
Conversation
|
Size Change: +2 B (0%) Total Size: 7.98 MB 📦 View Changed
ℹ️ View Unchanged
|
|
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. |
aduth
left a comment
There was a problem hiding this comment.
LGTM 👍 Tested combinations of cursor options and disabled states in local Storybook and works as expected.
I'm a bit surprised we missed this, but I guess it might have slipped unnoticed when we changed the default button cursor from default to pointer? i.e. Before then we didn't need to explicitly handle disabled styles.
Exactly! We already caught a few of these after that change 😄 |
|
Flaky tests detected in 54ebb58. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/26186152990
|
What?
Fixes the
@wordpress/uiButtoncursor style so disabled buttons do not receive the interactive control cursor.Why?
Disabled buttons should not visually suggest that they are interactive. The base button styles were applying
--wpds-cursor-controlregardless of the disabled state.How?
Only applies the control cursor when the button does not have
data-disabled. The existing link-specific cursor styling remains unchanged.Testing Instructions
Buttoncomponents.