fix(ui): use appropriate cursor type for readonly input fields #1208
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
sct
reviewed
Mar 17, 2021
TheCatLady
force-pushed
the
fix/ui/readonly-cursor
branch
from
2d2f627
to
dc2b75c
Compare
sct
approved these changes
Mar 18, 2021
|
🎉 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
readonlyinput fields cannot be interacted with, since otherwise they appear like regular text boxes. (Currently, there are only two such fields... the API key in General Settings, and the server name in Plex Settings.)Screenshot (if UI-related)
To-Dos
yarn buildIssues Fixed or Closed
N/A