luxolus
/
open-consul
2
0
Fork 0
Code Issues 1 Pull Requests Packages Releases Wiki Activity
open-consul/ui/packages/consul-ui/app/components/more-popover-menu/index.scss

41 lines
1.0 KiB
SCSS
Raw Normal View History

ui: Redesigns for the token/policy/roles listings pages (#8144)
2020-06-23 09:12:04 +00:00
.more-popover-menu {
ui: Token listing redesign (#8117)
2020-06-17 09:25:54 +00:00
@extend %more-popover-menu;
}
ui: Redesigns for the token/policy/roles listings pages (#8144)
2020-06-23 09:12:04 +00:00
%more-popover-menu {
ui: Extract and organize popover-menu and related from main-nav (#8272)
2020-07-09 13:26:52 +00:00
@extend %popover-menu;
ui: Token listing redesign (#8117)
2020-06-17 09:25:54 +00:00
}
ui: Extract and organize popover-menu and related from main-nav (#8272)
2020-07-09 13:26:52 +00:00
/* using the inut in the selector here means it won't */
/* take on the default :checked chevron icon */
%more-popover-menu .popover-menu > [type='checkbox'] + label {
ui: Redesigns for the token/policy/roles listings pages (#8144)
2020-06-23 09:12:04 +00:00
@extend %more-popover-menu-trigger;
ui: Token listing redesign (#8117)
2020-06-17 09:25:54 +00:00
}
ui: Redesigns for the token/policy/roles listings pages (#8144)
2020-06-23 09:12:04 +00:00
/* This gives the trigger a slightly larger invisible hit area */
%more-popover-menu-trigger {
padding: 7px;
ui: Token listing redesign (#8117)
2020-06-17 09:25:54 +00:00
}
ui: Redesigns for the token/policy/roles listings pages (#8144)
2020-06-23 09:12:04 +00:00
%more-popover-menu-trigger > * {
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
background-color: var(--transparent);
border-radius: var(--decor-radius-100);
ui: Extract and organize popover-menu and related from main-nav (#8272)
2020-07-09 13:26:52 +00:00
width: 30px;
height: 30px;
font-size: 0;
ui: Redesigns for the token/policy/roles listings pages (#8144)
2020-06-23 09:12:04 +00:00
}
%more-popover-menu-trigger > *::after {
@extend %with-more-horizontal-mask, %as-pseudo;
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
background-color: rgb(var(--tone-gray-900));
ui: Extract and organize popover-menu and related from main-nav (#8272)
2020-07-09 13:26:52 +00:00
width: 16px;
height: 16px;
position: absolute;
top: 50%;
left: 50%;
margin-top: -8px;
margin-left: -8px;
}
%more-popover-menu-trigger > *:active {
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
background-color: rgb(var(--tone-gray-100));
ui: Extract and organize popover-menu and related from main-nav (#8272)
2020-07-09 13:26:52 +00:00
}
%more-popover-menu-trigger > *:hover,
%more-popover-menu-trigger > *:focus {
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
background-color: rgb(var(--tone-gray-050));
ui: Redesigns for the token/policy/roles listings pages (#8144)
2020-06-23 09:12:04 +00:00
}