[SOLVED] Scrollbar on the recently updated Firefox

I'm just wondering if I'm the only one that noticed the scroll bar on regular pages in Firefox 68 is no longer using the one from the system GTK theme:


However, its internal pages do still use it:


I wonder if I'm missing something, here.

You are not... that royally pissed me off. I'll quote myself from a post in another thread here:

I have been angry today, that Firefox 68 no longer respects GTK styling for the scrollbar. It defaults to very ugly, thin, hard to grab, hard to see when short, grey scrollbars and grey scrollbar track. It uses my GTK+ style in preferences pages in the browser, but not on sites. This is likely related to website CSS being able to change it, my guess is that they enforced it so that would work consistently. I have a black GTK+ style with glowing orange to black gradient, that I am very fond of.

I can't get my hover gradient, but I can at least override the behaviour by creating a chrome/userContent.css file so I can see and grab my scrollbar again.

:root{
   scrollbar-color: #BA4A00 #000000;
   scrollbar-width: auto;
}

Based on information here:
https://developer.mozilla.org/en-US/...crollbar-color

The first colour value is for the scrollbar ("thumb") and the second is for the scrollbar track. As far as I can tell, scrollbar-width can be thin, auto, or none, with auto being OS defaults.

NOTE: In Firefox 68, they have disabled user customizations by default. Supposedly for "performance" they are no longer parsing userContent.css, userChrome.css, userChrome.xml etc. and you have to enable it in about:config

Toggle this value to True

toolkit.legacyUserProfileCustomizations.stylesheets

Thanks, TheRealGrogan. It's not so garish with my custom colours now. I didn't notice the outright lack of parsing user customisation files, because apparently I already had `toolkit.legacyUserProfileCustomizations.stylesheets` set to true.

Originally Posted by TheRealGrogan I can't get my hover gradient, but I can at least override the behaviour by creating a chrome/userContent.css file so I can see and grab my scrollbar again. :root{ scrollbar-color: #BA4A00 #000000; scrollbar-width: auto; } Based on information here: https://developer.mozilla.org/en-US/...crollbar-color The first colour value is for the scrollbar ("thumb") and the second is for the scrollbar track. As far as I can tell, scrollbar-width can be thin, auto, or none, with auto being OS defaults. NOTE: In Firefox 68, they have disabled user customizations by default. Supposedly for "performance" they are no longer parsing userContent.css, userChrome.css, userChrome.xml etc. and you have to enable it in about:config Toggle this value to True toolkit.legacyUserProfileCustomizations.stylesheets

Sorry if it's bad form to post to a "Solved" thread - I will repost as a new question if necessary?


I'm now on Firefox 70 with Numix theming, seeing the annoyingly thin scrollbars that are really difficult to grab and manipulate with the laptop touchpad. A different theme, e.g. Raleigh, shows thicker scrollbars.

Can you advise where I should put that "UserContent.css" file to have it picked up by Firefox, please? I'm on Xubuntu 18.04 if it's relevant.

Hey, no problem. It's not me that objects to that, my opinion is that it's best to keep things in context.

What you have to do, is create a directory in your ~/.mozilla profile. Your profile directory name will be randomly different, but mine is:

/home/grogan/.mozilla/firefox/30temyds.default/chrome

Create the chrome directory and put your userContent.css file in there.

Note that you may (or may not) have to go to about:config and toggle the following to true for those files to be parsed.

toolkit.legacyUserProfileCustomizations.stylesheets

@TheRealGrogan: You're a star!

It works beautifully (after I corrected my capitalisation of "userContent.css" ) and now my fat fingers can scroll up and down pages with ease again - and with a much prettier coloured scrollbar as an added extra.

Thanks so much for your help.

Oops, I typed that wrong in my last post too (corrected). It definitely matters on case sensitive filesystems :-)

Worked great for me!