Default List Display
Posted: Mon Nov 20, 2017 6:05 pm
I find myself popping around the same couple of pages that do not belong to the same category (e.g. "Bandwidth Usage" and "Quotas"), which means that I have to click through their "parents" each time that I do that.
Not a deal breaker, obviously, but I believe it would make Gargoyle much more user friendly if there were an option for people to turn off the default CSS which "hides" each list's children elements.
For anyone who might feel the way I do, I have accomplished this via a Chrome extension called "Stylebot".
And the following CSS:
Screenshot of result:
Enlarge
***
You could probably edit the CSS directly via SSH, but I didn't want to mess with that if I didn't have to.
The caveat with this method is that it isn't browser agnostic, and will need to be repeated in each browser that you use regularly. YMMV depending on availability of plugins/extensions.
EDIT
The extension at the time of this writing is throwing console errors for me (Chrome), but that may be due to a broken jQuery reference (in the extension) that doesn't affect the extension in the use case highlighted above.
Not a deal breaker, obviously, but I believe it would make Gargoyle much more user friendly if there were an option for people to turn off the default CSS which "hides" each list's children elements.
For anyone who might feel the way I do, I have accomplished this via a Chrome extension called "Stylebot".
And the following CSS:
Code: Select all
@media all and (min-width: 991px) {
#sidebar > ul > li > ul {
display: inline;
}
ul.sidebar .sidebar-list a {
font-size: 12px;
padding-left: 37px;
text-indent: 0;
border: 0;
font-weight: normal;
}
li.sidebar-item a {
border-bottom: none;
}
ul.sidebar .sidebar-list a:hover {
padding-left: none;
text-decoration: none;
}
}
Enlarge
***
You could probably edit the CSS directly via SSH, but I didn't want to mess with that if I didn't have to.
The caveat with this method is that it isn't browser agnostic, and will need to be repeated in each browser that you use regularly. YMMV depending on availability of plugins/extensions.
EDIT
The extension at the time of this writing is throwing console errors for me (Chrome), but that may be due to a broken jQuery reference (in the extension) that doesn't affect the extension in the use case highlighted above.