mirror of
https://github.com/status-im/consul.git
synced 2025-03-03 06:40:45 +00:00
b8166de30d
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
37 lines
864 B
SCSS
37 lines
864 B
SCSS
.topology-metrics-popover {
|
|
> button {
|
|
position: absolute;
|
|
transform: translate(-50%, -50%);
|
|
background-color: rgb(var(--white));
|
|
padding: 1px 1px;
|
|
&:hover {
|
|
cursor: pointer;
|
|
}
|
|
&:active,
|
|
&:focus {
|
|
outline: none;
|
|
}
|
|
&:disabled {
|
|
cursor: default;
|
|
}
|
|
}
|
|
&.deny .informed-action header::before {
|
|
display: none;
|
|
}
|
|
&.deny > button::before,
|
|
&.deny .tippy-arrow::after {
|
|
@extend %with-cancel-square-fill-mask, %as-pseudo;
|
|
background-color: rgb(var(--tone-red-500));
|
|
}
|
|
&.l7 > button::before,
|
|
&.l7 .tippy-arrow::after {
|
|
@extend %with-layers-mask, %as-pseudo;
|
|
background-color: rgb(var(--tone-gray-300));
|
|
}
|
|
&.not-defined > button::before,
|
|
&.not-defined .tippy-arrow::after {
|
|
@extend %with-alert-triangle-mask, %as-pseudo;
|
|
color: rgb(var(--tone-yellow-500));
|
|
}
|
|
}
|