2 ms·
or change userChrome.css The fact that you now need to set toolkit.legacyUserProfileCustomizations.stylesheets in order for userChrome.css to work, and that it
by userbinator 5y ago
or change userChrome.css
The fact that you now need to set toolkit.legacyUserProfileCustomizations.stylesheets in order for userChrome.css to work, and that it has "legacy" in the name, is already a sign that route might disappear in the future.
More "then[sic] any other browser" is a really low bar, especially when the others are far worse.
- lproven 5y agoThis is an excellent, key point. I use Waterfox these days, and occasionally Firefox if there's a problem. It's now significantly harder to customise either of them to the way I used to like pre-Quantum Firefox. A few more steps down this path and I won't be able to at all. https://www.theregister.com/2021/11/04/waterfox_firefox_fork/ https://www.theregister.com/2021/11/04/waterfox_firefox_fork...