fix(ui): use appropriate cursor type for disabled input elements #1184
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
TheCatLady
force-pushed
the
fix/ui/disabled-input-cursor
branch
2 times, most recently
from
7d9e9fb
to
8e6c26f
Compare
sct
approved these changes
Mar 16, 2021
TheCatLady
force-pushed
the
fix/ui/disabled-input-cursor
branch
from
8e6c26f
to
d250a92
Compare
|
馃帀 This PR is included in version 1.22.0 馃帀 The release is available on:
Your semantic-release bot 馃摝馃殌 |
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.
Description
Makes it clearer that disabled elements are disabled and cannot be interacted with. 馃樅
Screenshot (if UI-related)
To-Dos
yarn buildIssues Fixed or Closed
N/A