-
In this set of tokens, most semantic colors reference only the semantic part of the UX without attaching to a specific color palette. That's not the case with the border tokens where each border token is bound to the color palette: Should it be considered to add a set of semantic tokens specific only for the border states? + colorBorderActive: 'var(--colorBorderActive)',
+ colorBorder1: 'var(--colorBorder1)',
+ colorBorder2: 'var(--colorBorder2)', |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
@TristanWatanabe - FYI Is this the best place to discuss this? |
Beta Was this translation helpful? Give feedback.
-
@osfprieto this is a distinction between global and alias tokens. Our global color tokens come from a specified palette of colors and include tokens such as We also have alias color tokens, which depend on the global tokens and a provided brand ramp. These are the other type of tokens you see, such as Regarding your question about semantic tokens for border states, we do have them, they are just called
I hope this helps answer your question, let me know if there is anything else you have doubts about. |
Beta Was this translation helpful? Give feedback.
@osfprieto this is a distinction between global and alias tokens.
Our global color tokens come from a specified palette of colors and include tokens such as
colorPaletteAnchorBorderActive
above. You can normally notice which ones are global based on if they include the wordpalette
in them or not. Other examples arecolorPaletteBlueBackground1
andcolorPaletteTealForeground2
.We also have alias color tokens, which depend on the global tokens and a provided brand ramp. These are the other type of tokens you see, such as
colorNeutralForeground1
.Regarding your question about semantic tokens for border states, we do have them, they are just called
stroke
instead of border as they can also be…