2023-04-19 23:16:43 +12:00
|
|
|
/**
|
|
|
|
* Operations component styles
|
2023-04-20 14:59:22 +12:00
|
|
|
*
|
|
|
|
* For consistency sake I'm using an ID, but the custom wrapper / dropdown component
|
|
|
|
* can ( should ) be made into a reusable, generic component
|
2023-04-19 23:16:43 +12:00
|
|
|
*/
|
|
|
|
|
2023-04-20 14:59:22 +12:00
|
|
|
#operations-wrapper {
|
2023-04-19 23:16:43 +12:00
|
|
|
position: relative;
|
|
|
|
}
|
|
|
|
|
2023-04-20 14:59:22 +12:00
|
|
|
#operations-dropdown {
|
|
|
|
position: absolute;
|
|
|
|
top: 40px; /* the height of the input[type="search"] with pos relative */
|
|
|
|
width: 100%;
|
|
|
|
height: auto;
|
|
|
|
max-height: 60vh;
|
|
|
|
overflow: auto;
|
|
|
|
z-index: 20; /* to dropdown on top of all the other elements */
|
|
|
|
border-bottom: 1px solid var(--primary-border-colour);
|
|
|
|
}
|
|
|
|
|
2023-04-19 23:16:43 +12:00
|
|
|
#reset-operations.hidden,
|
|
|
|
#search-results.hidden,
|
|
|
|
#categories.hidden {
|
|
|
|
z-index: -10;
|
|
|
|
display: none;
|
|
|
|
}
|
2023-04-20 14:59:22 +12:00
|
|
|
|
|
|
|
@media only screen and ( min-width: 768px ){
|
|
|
|
#operations-dropdown {
|
|
|
|
border-bottom: none;
|
|
|
|
}
|
2023-04-20 18:33:03 +12:00
|
|
|
|
|
|
|
#search-results.hidden,
|
|
|
|
#categories.hidden {
|
|
|
|
z-index: initial;
|
|
|
|
display: block;
|
|
|
|
}
|
2023-04-20 14:59:22 +12:00
|
|
|
}
|