Firefox 69: userChrome.css and userContent.css disabled by default

[Karlston]

Mozilla plans to land a change in Firefox 69 that disables the loading of userChrome.css and userContent.css by default to improve performance.

 

The files userChrome.css and userContent.css are used to modify content of webpages or the browser itself using CSS instructions.

 

The option to do so is not removed but Mozilla plans to make it opt-in instead of opt-out. The organization states that not having to look for the two files on startup improves the start-up performance of the Firefox browser.

 

Firefox users who use the files already will have the feature enabled for them automatically to avoid disruptions to their workflows or expectations.

 

The preference needs to be flipped to True on new installations only starting with the release of Firefox 69.

 

Tip: check out customizing Firefox with userchrome.css.

 

Timeline for the change (proposed, subject to change):

• Firefox 68: Firefox checks if userChrome.css or userContent.css exist. If yes, preference will be set to True to allow the loading of these files on browser start. If no, preference remains set to False (don't look).
• Firefox 69: new installations will not support userChrome.css and userContent.css by default unless preference is set by the user.

The Preference that determines the state

 

The preference in question is toolkit.legacyUserProfileCustomizations.stylesheets. Here is how you change its value:

1. Load about:config in the Firefox address bar.
2. Confirm that you will be careful.
3. Search for toolkit.legacyUserProfileCustomizations.stylesheets using the search at the top.
4. Toggle the preference. True means Firefox supports the CSS files, False that it ignores them.

Closing Words

Options to load userChrome.css and userContent.css won't go away but users need to be aware that they may need to change the preference to allow the loading of these files from Firefox 69 onward.

 

The organization announced no plans to retire the option in the future.

 

Mozilla landed the User Scripts WebExtensions API recently in Firefox, but it appears unrelated to the change.

 

Source: Firefox 69: userChrome.css and userContent.css disabled by default (gHacks - Martin Brinkmann)