.CSS in v69 Requires About:Config Mod

Discussion about official Mozilla Firefox builds

User avatar
Posts: 438
Joined: July 14th, 2004, 5:03 am

Post Posted May 23rd, 2019, 2:16 am ... 541233#c35

The last posts in the above link talk about advising this Forum of the following .........
Turns out the time it takes a Profile to look for a Chrome Folder & contents at Startup (about 80 files are queried for) is Longer than reading/reacting to a pref that lets .css work.
In the spirit of Startup time not being improved with a few genius mods netting Big Startup time savings, but rather with a ton of little ones, there was a discussion about the need for a Chrome folder/css - Vs - letting Extensions do the customizations.

Thankfully logic has won so far and, as of now, a new -- about:config -- entry -- toolkit.legacyUserProfileCustomizations.stylesheets -- will need to be Changed to TRUE in v69 for - user and content.css - to continue working. This means non-Chrome users will have browser start-up "x ms" sooner than we will, & (presumably) satisfies the design team decision makers that loss of - x ms - startup improvements is a choice and not of poor design.
Firefox 89 - Win 10 Pro 21H1 - Diapers, Politicians, and the Media ... ALL Need Changing for the Same Reason - uBO - Cookie AutoDelete - Privacy Possum - LocalCDN - CSS Exfil - HTTPS Everywhere - SingleFile - Reader View - History Cleaner -


User avatar
Posts: 20689
Joined: March 10th, 2004, 9:59 pm
Location: Maryland USA

Post Posted May 23rd, 2019, 11:24 am

"Speed", bragging rights, whatever you want to say, whatever excuse you want to use, Trumps all, so logic is out the door.
Fire 750, bring back 250.
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv: Gecko/20110420 SeaMonkey/2.0.14 Pinball CopyURL+ FetchTextURL FlashGot NoScript


User avatar
Posts: 9908
Joined: November 4th, 2006, 7:07 pm
Location: Hollywood Ca.

Post Posted May 23rd, 2019, 11:37 am

What a bunch of BS, like we don't know the real reason this has suddenly come up.
The old tried and tested MozCo 'kill it softly' move...
#KeepFightingMichael and Alex.


User avatar
Posts: 53384
Joined: July 18th, 2005, 3:25 am

Post Posted May 23rd, 2019, 12:50 pm

This should work automatically if you update your current profile regularly.

Bug 1550157 - Set a pref in the user profile if a userChrome.css or userContent.css file exists in the profile directory [68]

In preparation for the plan in bug 1541233 comment 23, I want to land a patch that detects if userChrome.css or userContent.css exists in the user profile, and if so, sets a pref.

I'm hoping to get this into Firefox 68 so that in Firefox 69, we can avoid attempting to load those files at all unless the pref is set.

Doing it this way avoids headache for the users that have userChrome.css / userContent.css and don't want to flip a pref to keep using them.

Posts: 1199
Joined: December 27th, 2017, 4:03 am
Location: Australia

Post Posted May 24th, 2019, 6:31 pm

IMO this was predicted ages ago that Mozilla would do this, its just another step towards Mozilla permanently killing it off.

Return to Firefox Builds

Who is online

Users browsing this forum: No registered users and 2 guests