-
Notifications
You must be signed in to change notification settings - Fork 70
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
Introduce $ouiInfoColor and $ouiInfoLinkColor #1161
Comments
We should start with callout (info) and add a new option to toast (info) |
Button & Link i would want to consider a bit more |
One more request for mapping for |
Badging colors are currently unaffected by this as "primary" badge color still displays as blue but we can certainly consider updating the naming schema for badging. |
There is currently an Info toast, we just need to modify and add the indicator top border to it. I can add an issue for follow-up. |
This issue is for adding the color variables |
I can take this on! |
Is your feature request related to a problem? Please describe.
Currently OpenSearch UI currently maps information link colors to ouiColorPrimary or ouiLinkColor. This creates a conflict in color indication when we move to Next dark/light as Primary and Secondary/Success colors map to a green tone which makes it difficult and confusing for a customer user to differentiate between the meaning of the indicated color, primarily in callouts and information related links.
Describe the solution you'd like
We would like to introduce two new variables:
$ouiInfoColor - using a color that is significantly different from $ouiColorPrimary
$ouiInfoColorLink - using a color that is significantly different from $ouiLinkColor
$ouiLinkColor / $ouiInfoLinkColor:
Next Dark:
#0FABFF
Next Light:
#1390E6
Describe alternatives you've considered
Additional context
Components that should map to this color:
Callout (Info)
Info button type in all styles and sizes
Health - Active state
(May add more to this list - progress?)
Adding @kgcreative for visibility
The text was updated successfully, but these errors were encountered: