-
Notifications
You must be signed in to change notification settings - Fork 535
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deprecate and remove the input contrast
prop
#4355
Comments
If this is important, could we just change the input to have a |
I'm worried about a default transparent background breaking designs where we're only able to reach the 3:1 contrast minimum because of the white input background. I think this use-case is pretty rare and can be safely handled with style overrides. |
Hi! This issue has been marked as stale because it has been open with no activity for 180 days. You can comment on the issue or remove the stale label to keep it open. If you do nothing, this issue will be closed in 7 days. |
The
contrast
prop, when applied toSelect
,TextInput
, orTextarea
(one would also expect it onTextInputWithTokens
but it's not available there) renders an input with a subtle background, somewhere between the default and disabled styling:In dark theme it has no effect:
The documentation says this prop:
But ironically it actually reduces the contrast between the text and background.
This prop is problematic because, as shown above, it can make active inputs look disabled. This can and has caused confusion for users, and so the recommendation and effort has been to avoid using it in GitHub UI (including in PVC components). We've been considering getting rid of it for a while, so let's get it done.
The text was updated successfully, but these errors were encountered: