John Cowen b8166de30d
ui: Replaces almost all remaining instances of SASS variables with CSS (#11200)
From an engineers perspective, whenever specifying colors from now on we should use the form:

```
color: rgb(var(--tone-red-500));
```

Please note:

- Use rgb. This lets us do this like rgb(var(--tone-red-500) / 10%) so we can use a 10% opacity red-500 if we ever need to whilst still making use of our color tokens.
- Use --tone-colorName-000 (so the prefix tone). Previously we could use a mix of --gray-500: $gray-500 (note the left hand CSS prop and right hand SASS var) for the things we need to theme currently. As we no longer use SASS we can't do --gray-500: --gray-500, so we now do --tone-gray-500: --gray-500.

Just for clarity after that, whenever specifying a color anywhere, use rgb and --tone. There is only one reason where you might not use tone, and that is if you never want a color to be affected by a theme (for example a background shadow probably always should use --black)

There are a 2 or 3 left for the code editor, plus our custom-query values
2021-10-07 19:21:11 +01:00

40 lines
870 B
SCSS

%tab-nav ul {
list-style-type: none;
}
%tab-nav label {
cursor: pointer;
}
%tab-button {
white-space: nowrap;
text-decoration: none;
}
%tab-nav {
/* %frame-transparent-something */
border-bottom: var(--decor-border-100);
}
%with-animated-tab-selection ul::after,
%tab-button {
border-bottom: var(--decor-border-300);
}
%tab-nav {
/* %frame-transparent-something */
border-color: rgb(var(--tone-gray-200));
}
%tab-button {
@extend %with-transition-500;
transition-property: background-color, border-color;
border-color: var(--transparent);
color: rgb(var(--tone-gray-500));
}
%tab-button-intent,
%tab-button-active {
/* %frame-gray-something */
background-color: rgb(var(--tone-gray-100));
}
%tab-button-intent {
border-color: rgb(var(--tone-gray-300));
}
%tab-nav.animatable .selected a {
border-color: var(--transparent) !important;
}