7c56d99fc1
In the material theme, if the screen is too narrow, the navigation pane becomes a collapsable "hamburger-menu" style button. Currently, on the containers page, when that button is pressed the navigation pane is below the containers list. This makes navigation impossible. See screenshot here: http://i.imgur.com/uzdX66E.png Adjusting the z-index of the container down from 10 to 2 aleviates this issue. Obviously the containers page is being reworked elsewhere; so keeping this change as small as possible is appropriate. Change-Id: I220d2f8a87e9a55b95884251b3368abe1167cafa Closes-Bug: 1552898 Partially-implements: blueprint horizon-theme-css-reorg
165 lines
3.2 KiB
SCSS
165 lines
3.2 KiB
SCSS
/* ResourceBrowser style */
|
|
|
|
#browser_wrapper {
|
|
width: $rbrowser-wrapper-width;
|
|
min-width: 1000px;
|
|
background-color: $rbrowser-header-background-color;
|
|
border: $rbrowser-data-table-border-width solid $rbrowser-data-table-border-color;
|
|
border-radius: 4px;
|
|
|
|
.tfoot {
|
|
clear: both;
|
|
padding: 8px;
|
|
border-top: 1px solid $rbrowser-data-table-border-color;
|
|
background-color: $rbrowser-footer-background-color;
|
|
font-size: 11px;
|
|
line-height: 14px;
|
|
|
|
span {
|
|
display: inline-block;
|
|
|
|
&.navigation_table_count {
|
|
width: $rbrowser-navigation-table-width;
|
|
}
|
|
}
|
|
}
|
|
|
|
form,
|
|
table {
|
|
margin-bottom: 0;
|
|
}
|
|
|
|
.navigation_wrapper,
|
|
.content_wrapper {
|
|
position: relative;
|
|
float: left;
|
|
}
|
|
|
|
div.navigation_wrapper {
|
|
z-index: 2;
|
|
width: $rbrowser-navigation-table-width;
|
|
|
|
div.table_wrapper,
|
|
thead th.table_header {
|
|
border-right: 0 none;
|
|
border-top-right-radius: 0;
|
|
}
|
|
|
|
td {
|
|
&:first-child {
|
|
border-left: 0 none;
|
|
}
|
|
|
|
&.breadcrumb_td {
|
|
padding-right: 0;
|
|
max-width: 200px;
|
|
}
|
|
}
|
|
|
|
tr.current_selected td {
|
|
background-color: $rbrowser-selected-color;
|
|
}
|
|
|
|
tfoot td {
|
|
border-right: 0 none;
|
|
border-bottom-right-radius: 0;
|
|
}
|
|
|
|
ul.breadcrumb {
|
|
padding-right: 0;
|
|
border-top-right-radius: 0;
|
|
border-bottom-right-radius: 0;
|
|
border-right: 0;
|
|
white-space: nowrap;
|
|
}
|
|
|
|
tbody td {
|
|
border-right: $rbrowser-data-table-border-width solid $rbrowser-data-table-border-color;
|
|
background-color: $rbrowser-body-background-color;
|
|
|
|
&.anchor {
|
|
word-wrap: break-word;
|
|
white-space: normal;
|
|
max-width: 145px;
|
|
}
|
|
}
|
|
}
|
|
|
|
div.content_wrapper {
|
|
width: $rbrowser-content-table-width;
|
|
|
|
div.table_wrapper,
|
|
thead th.table_header {
|
|
border-left: 0 none;
|
|
border-top-left-radius: 0;
|
|
}
|
|
|
|
td {
|
|
border-bottom: $rbrowser-data-table-border-width solid $rbrowser-data-table-border-color;
|
|
|
|
&:last-child {
|
|
border-right: 0 none;
|
|
}
|
|
|
|
&.breadcrumb_td {
|
|
padding-left: 0;
|
|
}
|
|
}
|
|
|
|
tfoot td {
|
|
border-left: 0 none;
|
|
border-bottom-left-radius: 0;
|
|
}
|
|
|
|
/* FIXME(Ke Wu): for now there are two breadcrumb tr in both table
|
|
* and this one in the content table is hidden. This hack is made to
|
|
* fix the alignment of two table, needs a better solution in the
|
|
* future.
|
|
*/
|
|
ul.breadcrumb {
|
|
padding-left: 0;
|
|
border-top-left-radius: 0;
|
|
border-bottom-left-radius: 0;
|
|
border-left: 0;
|
|
|
|
li {
|
|
visibility: hidden;
|
|
}
|
|
}
|
|
}
|
|
|
|
table {
|
|
border-collapse: collapse;
|
|
|
|
thead {
|
|
tr th {
|
|
border-bottom: 0;
|
|
background-color: $rbrowser-header-background-color;
|
|
}
|
|
}
|
|
|
|
tbody {
|
|
tr {
|
|
&:last-child td {
|
|
border-bottom: 1px solid $rbrowser-data-table-border-color;
|
|
border-radius: 0;
|
|
}
|
|
|
|
&.empty td {
|
|
height: $rbrowser-td-height;
|
|
padding: $rbrowser-actions-column-padding;
|
|
}
|
|
}
|
|
|
|
td.actions_column {
|
|
position: static;
|
|
}
|
|
}
|
|
}
|
|
|
|
.breadcrumb {
|
|
padding: 6px;
|
|
margin: 0 0 1px;
|
|
}
|
|
}
|