You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Red-50 being used for error messages is not accessible on Gray80 or Gray70 in the dark themes. We need to add a new token that controls the value of the error messages that's not attached to support-01. The name we want to go with is text-error but also open to that since it a little breaks our token naming logic.
To-do:
Add new $text-error token
Update $support-01 in Gray-90 Theme to Red-40 #ff8389
Update all invalid messages in components to use new $text-error token (replaces $support-01)
$text-error
White
Gray 10
Gray 90
Gray 100
V9
Red-60 / #da1e28
Red-60 / #da1e28
Red-30 #ffb3b8
Red-40 #ff8389
#e0182d
The text was updated successfully, but these errors were encountered:
@aagonzales do you know which specific components will need to have this token updated? Or is it just all instances of support-01 should now be text-error?
Its not all instances of support-01 only instances of support-01 that are text. So basically text in invalid states, which I think are mostly inputs. I can make a list if that's easier.
Red-50 being used for error messages is not accessible on Gray80 or Gray70 in the dark themes. We need to add a new token that controls the value of the error messages that's not attached to
support-01
. The name we want to go with istext-error
but also open to that since it a little breaks our token naming logic.To-do:
$text-error
token$support-01
in Gray-90 Theme to Red-40#ff8389
$text-error
token (replaces$support-01
)$text-error
#da1e28
#da1e28
#ffb3b8
#ff8389
#e0182d
The text was updated successfully, but these errors were encountered: