-
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
Components: Add isFocusable state to Button #19337
Merged
Merged
Changes from 1 commit
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
21e3c9c
Components: Add isFocusable state to Button
diegohaz 9fb891f
Make isFocusable true by default
diegohaz b1957ac
Update styles
diegohaz 452926c
Remove stopImmediatePropagation call
diegohaz 25a0fb3
Fix unit tests
diegohaz 3bc6257
Fix e2e tests
diegohaz db17a04
Merge branch 'master' into update/button-is-focusable
diegohaz 8d9bb96
Make isFocusable prop experimental and false by default
diegohaz File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -46,7 +46,7 @@ | |
|
||
} | ||
|
||
&:active:enabled { | ||
&:not([aria-disabled="true"]):active:enabled { | ||
background: #f3f5f6; | ||
color: color(theme(button) shade(5%)); | ||
border-color: #7e8993; | ||
|
@@ -87,7 +87,7 @@ | |
0 0 0 3px color(theme(button)); | ||
} | ||
|
||
&:active:enabled { | ||
&:not([aria-disabled="true"]):active:enabled { | ||
background: color(theme(button) shade(20%)); | ||
border-color: color(theme(button) shade(20%)); | ||
color: $white; | ||
|
@@ -149,7 +149,7 @@ | |
height: auto; | ||
|
||
&:not(:disabled):not([aria-disabled="true"]):hover, | ||
&:active { | ||
&:not([aria-disabled="true"]):active { | ||
color: #00a0d2; | ||
} | ||
|
||
|
@@ -166,7 +166,7 @@ | |
color: $alert-red; | ||
} | ||
|
||
&:active { | ||
&:not([aria-disabled="true"]):active { | ||
color: inherit; | ||
} | ||
|
||
|
@@ -212,7 +212,7 @@ | |
outline: none; | ||
} | ||
|
||
&:active:focus:enabled { | ||
&:not([aria-disabled="true"]):active:focus { | ||
box-shadow: none; | ||
} | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The styles changes make me a bit nervous :P because we have some many button styles ovverrides in the UI that I know this can trigger specificity issues and should be tested properly. |
||
|
||
|
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
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.
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.
Should this default to true instead? I feel this was needed in every disabled button we have in the UI. I'm even wondering if we need a prop or just do this automatically.
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.
Now, it makes me wonder how often we want to have a button which is both disabled and not focusable at the same time. It feels like for accessibility reasons it should always be focusable.
https://ux.stackexchange.com/questions/103239/should-disabled-elements-be-focusable-for-accessibility-purposes - it only confirms this reasoning.
It might be a good idea to set isFocusable to true by default as suggested.
We might be some disabled and not focusable buttons but it might be simply wrong. We should found those cases and take further steps based on that.
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.
Made
isFocusable
true by default