Right, background-color
is not an inherited property (compared to for example color
(color of text) which is). But even if it were, inheritance is not “enforced” so if website css sets a backround-color specifically for that element then the inherited value would be lost anyway.
But the way you now describe it doesn’t seem possible. There is not syntax to apply style rule to “just the innermost element”. I think the closest would be to have everything else have fully transparent background, but the html root element have only partial transparency:
*{
background: transparent !important;
}
html:root{
background: #00000080 !important;
}
However, you will still face a problem; many websites draw graphics or images as a background-image
so if you use the background
shorthand property then those graphics will be effectively removed. On the other hand, if you instead set just background-color
then parts might get opaque again because a website could be drawing even opaque backgrounds as background-image instead of background-color.
You can hide them with userContent.css - most of the devtools window stuff is styled via userContent.css not userChrome.css.
But there’s a catch.
Browser toolbox is essentially a separate instance of Firefox, running in separate profile so your “normal” user css files don’t apply to it. Thus, you need to first enable the toolbox profile to load it’s own user css files and create them just like you do normally (toggle
toolkit.legacyUserProfileCustomizations.stylesheets
, create files inchrome/
folder etc.). The toolbox profile is stored inside the regular profile - in a directorychrome_debugger_profile
.To get to
about:config
of the toolbox profile you need to first open a new main-window for it - one way that works is to click the meatball menu at the top-right of the toolbox window, and select “Documentation…” - that will launch a new window using using the toolbox profile and then you can just open about:config and proceed as usual. Or you can just modify prefs.js of the toolbox profile directly while the toolbox is not running.Anyway, after you have set up the toolbox window to load user css files, then just slap this to its userContent.css and restart the toolbox:
header.chrome-debug-toolbar{ display: none !important; }