Re: userChrome.css and userContent.css disabled by default in Fx 69+
- Date: Tue, 28 May 2019 10:37:03 -0500
- From: »Q« <boxcars@xxxxxxx>
- Subject: Re: userChrome.css and userContent.css disabled by default in Fx 69+
Sailfish <NIXCAPSsailfish@xxxxxxxxxxxxxxxxxxxxxxxx> wrote:
> My bloviated meandering follows what »Q« graced us with on 5/24/2019
> 6:31 AM:
> > tl;dr: In Fx 69+, using userChrome.css and userContent.css will be
> > controlled by a pref which will be off in new profiles. Fx 68 will
> > toggle it on in profiles currently using either of those files.
> > <https://www.ghacks.net/2019/05/24/firefox-69-userchrome-css-and-usercontent-css-disabled-by-default/>
> > <https://bugzilla.mozilla.org/show_bug.cgi?id=1541233>
> Since I don't wish to remember this when it comes to pass, I added it
> to my user.js file. Should be fine unless Mozilla decides to no
> longer support that.
I use Stylish for what I used to have in userContent.css, and I just
realized everything in my userChrome.css is commented out. I think it
stopped working when Australis was released and I never got around to
trying to tweak Australis or Quantum with it.
Also, I thought userChrome.css only applied to xul and that most or
all of the xul had already been ripped out of Fx.
general mailing list