.CSS in v69 Requires About:Config Mod

[costark]

https://bugzilla.mozilla.org/show_bug.c ... 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.

[therube]

"Speed", bragging rights, whatever you want to say, whatever excuse you want to use, Trumps all, so logic is out the door.

[mightyglydd]

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...

[dickvl]

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

See:
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.

[Snake4]

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