fix(VNumberInput): disable keyboard up/down for readonly state #19906
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
VNumberInput should keep original value as long as it has
readonly
, ordisabled
attributes or is contained withinreadonly
form. (similar to other controls).Fix is inspired by similar change for VAutocomplete and aims to render controls as disabled instead of just suppressing event handlers. Test cases should be self-explanatory.
Idea to consider: hiding controls and showing
mdi-lock-outline
instead would be a nice touch, but should probably follow internal discussion about consistency with other components acceptingreadonly
prop.fixes #19896
Playground: