Web lists-archives.com

Re: userChrome.css and userContent.css disabled by default in Fx 69+




In <news:yuOdnV3k4uAz_nDBnZ2dnUU7-SnNnZ2d@xxxxxxxxxxx>,
Sailfish <NIXCAPSsailfish@xxxxxxxxxxxxxxxxxxxxxxxx> wrote:

> My bloviated meandering follows what »Q« graced us with on 5/28/2019 
> 8:37 AM:
> > In <news:rK-dnfkdO5wwAHbBnZ2dnUU7-aOdnZ2d@xxxxxxxxxxx>,
> > 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  only applied to xul and that most or
> > all of the xul had already been ripped out of Fx.   
> >   
> Fx chrome/userChrome.css affects browser's chrome element styles and 
> while chrome/userContent.css affects browser content window styles.
> I've not heard where Mozilla has hidden element styles yet.
> 
> Here's an obvious example to test with.
> 1. Bring up Fx67 <- Latest production release
> 2. Open bookmarks panel (Ctl+B) and note size of font
> 3. Close Fx67
> 4. Add stylesheet change below to chrome/userChrome.css
> 
> /*
>   * Make all the default font sizes 20 pt:
>   */
>   * {
>     font-size: 20pt !important
>   }
> 
> 5. Open Fx67 and note size of font.
>     WARNING! May induce anxious palpitations! :_)
> 
> However, CSS files used to be able to support overlays which would 
> afford some control over modifying the underlying XUL structures but 
> that was nixed due to security concerns even before complete themes
> were ingloriously thrown under the bus. Perhaps that's what you are
> recollecting?

My misunderstanding was simpler than that -- I'd read (without paying
very much attention) that they're getting rid of xul files entirely.
It's true, they are, but after a bit of poking around just now, I see
the xul is being replaced by html and xhtml*.  Both of those can be
styled with css, so I guess userChrome.css will go on styling the
chrome.

* For example, as of just a few days ago, browser.xul has been replaced
  by browser.xhtml.
  <https://bugzilla.mozilla.org/show_bug.cgi?id=1533881>

  


_______________________________________________
general mailing list
general@xxxxxxxxxxxxxxxxx
https://lists.mozilla.org/listinfo/general