Closed Bug 1550157 Opened 7 months ago Closed 7 months ago

Set a pref in the user profile if a userChrome.css or userContent.css file exists in the profile directory

Categories

(Core :: CSS Parsing and Computation, enhancement)

enhancement
Not set

Tracking

()

RESOLVED FIXED
mozilla68
Tracking Status
firefox68 --- fixed

People

(Reporter: mconley, Assigned: mconley)

References

Details

Attachments

(1 file)

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.

This is in preparation to disable (but not remove) support for these customizations
by default. We want to avoid scanning for these files on start-up, but also don't want
to make our users jump through a pref-flipping hoop to get their customizations back.

So we'll detect those files and flip the pref for this release. For the next release,
we'll not load those files unless the pref is flipped.

Pushed by mconley@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/efc907d677c2
Set a pref if the user profile is using a userChrome.css or userContent.css file. r=emilio
Status: NEW → RESOLVED
Closed: 7 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla68
Blocks: 1543096

"toolkit.legacyUserProfileCustomizations.stylesheets"

Firefox 68 unabled my carefully css-customized colored scrollbar back to the standard grey color. The "toolkit.legacyUserProfileCustomizations.stylesheets" setting to "true" does NOT solve this. Now my scrollbar is stuck at the almost invisible grey color. What is wrong?

"advocacy"

I forgot censorship

You need to log in before you can comment on or make changes to this bug.