fix: Input, InputNumber, TextArea disabled attribute fix #1048
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
ElderJames
approved these changes
Jan 27, 2021
@anddrzejb I think it is we missing them. |
ElderJames
pushed a commit
that referenced
this pull request
Apr 23, 2022
ElderJames
pushed a commit
that referenced
this pull request
Apr 30, 2022
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.
馃 This is a ...
馃敆 Related issue link
#1047
馃挕 Background and solution
Missing
disabledattribute oninputelement.There is a certain assumption here (visible in the changes in
Input.cs): ifdisabledattribute is set totruein any fashion, it will always prevail.BTW: @ElderJames I noticed that for example
Cascadercomponent does not haveDisabledproperty. Is this by design?鈽戯笍 Self Check before Merge