-
Notifications
You must be signed in to change notification settings - Fork 870
[Inputs] Styles should prioritize disabled over readOnly #8239
Copy link
Copy link
Labels
design decisionUse this to flag an item that needs input from the design teamUse this to flag an item that needs input from the design teamhelp wantedThe EUI team is unlikely prioritize. (Don't delete - used for automation)The EUI team is unlikely prioritize. (Don't delete - used for automation)low hanging fruitAn issue, often a bug, that is lower effort and clearly ought to be fixedAn issue, often a bug, that is lower effort and clearly ought to be fixed
Metadata
Metadata
Assignees
Labels
design decisionUse this to flag an item that needs input from the design teamUse this to flag an item that needs input from the design teamhelp wantedThe EUI team is unlikely prioritize. (Don't delete - used for automation)The EUI team is unlikely prioritize. (Don't delete - used for automation)low hanging fruitAn issue, often a bug, that is lower effort and clearly ought to be fixedAn issue, often a bug, that is lower effort and clearly ought to be fixed
Type
Fields
Give feedbackNo fields configured for Enhancement.
Is your feature request related to a problem? Please describe.
Related to #8238, a solution to this would be to set
readOnlywheneverdisabledis set, so something like this...The issue in this case is that the current styles prioritize
readOnlywhenever bothreadOnlyanddisabledare applied together.See demo https://codesandbox.io/p/sandbox/adoring-christian-jk8t45
Describe the solution you'd like
The input styles prioritize
disabledoverreadOnly. This is the same behavior as the basic html input.Describe alternatives you've considered
An alternate fix to #8238 would be to just check
disabledbefore triggeringonChangefrom a consumers perspective, but this is not ideal.Desired timeline
Unknown
cc: @MichaelMarcialis