Removing pointer events from disabled button components. #4435
Conversation
|
I'm not a maintainer, but I wonder if this is something where the I would expect native browser behavior to handle the default disabled interaction. If the design system wants to add a "pointer" styling to indicate that a button is interactive, it should only do so for buttons which are actually interactive (i.e. not disabled buttons). |
|
It's not just the changes to the cursor, either, it seems like if you do things like make an outlined button disabled you get unintentional style changes on hover. |
mejiaj
left a comment
mejiaj
left a comment
There was a problem hiding this comment.
Hey, @hatfieldMichael. Thanks for the contribution!
The cursor: pointer styling was removed in release 2.12.0 in PR #4132. The issue at that time was to prevent users from adding the .usa-button--disabled class and instead have them use the disabled attribute.
I agree with @aduth, maybe we should remove cursor: pointer; on .usa-button:15 and add it to non-disabled buttons.
.usa-button {
…
&:not([disabled]) {
cursor: pointer;
}
|
@mahoneycm can you confirm if this issue still applies with your work on disabled styles? |
|
Closing in favor of #5063 |
5 participants
Removing pointer events from disabled button components.
Description
Disabled buttons shouldn't interact with the cursor and suggest to the user that they are interactive elements.