github
/
consul
mirror of https://github.com/hashicorp/consul
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
consul/ui/packages/consul-ui/app/components/overlay/square-tail.scss

51 lines
1.2 KiB
SCSS
Raw Normal View History

ui: Fixup prettier for scss files and run (#10296) * ui: Ensure prettier makes all our scss files pretty * Run prettier on all our scss files
2021-05-27 12:23:54 +00:00
[data-theme~='square-tail'] {
ui: New overlays (#9305) Replaces ember-popover with tippy.js based overlay modifier.
2020-12-02 09:43:34 +00:00
.tippy-arrow {
--size: 18px;
left: calc(0px - (var(--size) / 2)) !important;
}
.tippy-arrow::before {
ui: Fix brand coloring for inline-code plus docs (#11578) * ui: Fix brand coloring for inline-code plus docs Also use --tones instead of --black/--white (#11601) Co-authored-by: Evan Rowe <ev.rowe@gmail.com>
2021-11-23 18:32:11 +00:00
background-color: rgb(var(--tone-gray-000));
ui: New overlays (#9305) Replaces ember-popover with tippy.js based overlay modifier.
2020-12-02 09:43:34 +00:00
width: calc(1px + var(--size));
height: calc(1px + var(--size));
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 18:21:11 +00:00
border: var(--decor-border-100);
border-color: rgb(var(--tone-gray-300));
ui: New overlays (#9305) Replaces ember-popover with tippy.js based overlay modifier.
2020-12-02 09:43:34 +00:00
}
// potential icon
.tippy-arrow::after {
position: absolute;
left: 1px;
}
ui: Fixup prettier for scss files and run (#10296) * ui: Ensure prettier makes all our scss files pretty * Run prettier on all our scss files
2021-05-27 12:23:54 +00:00
&[data-placement^='top'] {
ui: New overlays (#9305) Replaces ember-popover with tippy.js based overlay modifier.
2020-12-02 09:43:34 +00:00
& {
bottom: -10px;
}
.informed-action {
border-bottom-left-radius: 0 !important;
}
.tippy-arrow::before {
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 18:21:11 +00:00
border-bottom-left-radius: var(--decor-radius-200);
border-bottom-right-radius: var(--decor-radius-200);
ui: New overlays (#9305) Replaces ember-popover with tippy.js based overlay modifier.
2020-12-02 09:43:34 +00:00
border-top: 0 !important;
}
.tippy-arrow::after {
bottom: calc(0px - var(--size));
}
}
ui: Fixup prettier for scss files and run (#10296) * ui: Ensure prettier makes all our scss files pretty * Run prettier on all our scss files
2021-05-27 12:23:54 +00:00
&[data-placement^='bottom'] {
ui: New overlays (#9305) Replaces ember-popover with tippy.js based overlay modifier.
2020-12-02 09:43:34 +00:00
& {
top: -10px;
}
.informed-action {
border-top-left-radius: 0 !important;
}
.tippy-arrow::before {
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 18:21:11 +00:00
border-top-left-radius: var(--decor-radius-200);
border-top-right-radius: var(--decor-radius-200);
ui: New overlays (#9305) Replaces ember-popover with tippy.js based overlay modifier.
2020-12-02 09:43:34 +00:00
border-bottom: 0 !important;
}
.tippy-arrow::after {
top: calc(0px - var(--size));
}
}
}