Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

Learn More

userChrome not working

  • 5 réponses
  • 1 a ce problème
  • 4 vues
  • Dernière réponse par cor-el

more options

Fx 69.01a (Nightly)
Fx 69.0b2 (Dev Edition)
Fx 68.0 ("raw" Beta)
Fx 67.0.4 (Release)
Windows 7

In the current Fx release the hidden preference (about:config)
"toolkit.legacyUserProfileCustomizations.stylesheets"
is not relevant so it is obvious that my "userCrome.css" works perfectly in that Profile.

I am, however, somewhat perplexed that in the profiles using Fx v68 and Fx v69 userCrome.css does not work even though the value of "toolkit.legacyUserProfileCustomizations.stylesheets" is set to "true".

I have spent a chink of time (not so long as a chunk) building a new post-v67 profile without any extensions and without any other hidden prefs in case there was a conflict but to no avail. "toolkit.legacyUserProfileCustomizations.stylesheets = true" does nothing - userChrome is ignored.

Is there some other needs-to-be-flipped pref that Mozilla forgot to tell us about or is there something wrong with the flipping code (in all senses)?
Or something else?

Fx 69.01a (Nightly)<br> Fx 69.0b2 (Dev Edition)<br> Fx 68.0 ("raw" Beta)<br> Fx 67.0.4 (Release)<br> Windows 7 <br><br> In the current Fx release the hidden preference (about:config) <br>"toolkit.legacyUserProfileCustomizations.stylesheets"<br> is not relevant so it is obvious that my "userCrome.css" works perfectly in that Profile.<br><br> I am, however, somewhat perplexed that in the profiles using Fx v68 and Fx v69 userCrome.css does not work even though the value of "toolkit.legacyUserProfileCustomizations.stylesheets" is set to "true".<br><br> I have spent a chink of time (not so long as a chunk) building a new post-v67 profile without any extensions and without any other hidden prefs in case there was a conflict but to no avail. "toolkit.legacyUserProfileCustomizations.stylesheets = true" does nothing - userChrome is ignored. <br><br> Is there some other needs-to-be-flipped pref that Mozilla forgot to tell us about or is there something wrong with the flipping code (in all senses)? <br>Or something else?

Modifié le par concentricbrainwaves

Toutes les réponses (5)

more options

It should work in Firefox 69 with the pref set to true. I haven't noticed any issues with migrating from 68 to 69. Firefox 68 sets this pref silently when userChrome.css or userContent.css is detected to make it easier to update to 69 without these files getting disabled. Developer Edition is currently 69 (69.0b2), so does require this pref.

Did this still work in 68 because that version didn't disable these files? If it failed there as well then sometnig is wrong with the files (possible hidden .txt or .css file extension). You can open the file in a Firefox tab for inspection.


1541233 - Stop loading userContent.css or userChrome.css by default unless a preference is set [69] 1550157 - Set a pref in the user profile if a userChrome.css or userContent.css file exists in the profile directory [68]

more options

@Corel Thanks but I already knew all of that (including the bug references).
Interestingly in Fx 68 (which auto flipped the files) it worked but now - still in 68 with the auto-flip still flipped - it does not work,
In 69 with the pref manually set it does not work.

This, as said, is in a clean new profile with no extensions and no other config changes.

Modifié le par concentricbrainwaves

more options

Like I wrote above, if it doesn't work in 68 as well then something is wrong with the file(s) and you need to check that.

more options

May I ask "which file(s)" ? Daft question, but how can "files" be at fault in a new profile?

Modifié le par concentricbrainwaves

more options

is is obviously about the userChrome.css file you claim isn't working. I assume that you created the chrome folder in the new profile and placed your userChrome.css file in this folder?


It is not that difficult to create userChrome.css if you have never used it.

The first step is to open the "Help -> Troubleshooting Information" page and find the button to access the profile folder.

You can find this button under the "Application Basics" section as "Profile Folder -> Open Folder". If you click this button then you open the profile folder in the Windows File Explorer. You need to create a folder with the name chrome in this folder (name is all lowercase). In the chrome folder you need to create a text file with the name userChrome.css (name is case sensitive). In this userChrome.css text file you paste the text posted. On Mac you can use the TextEdit utility to create the userChrome.css file as a plain text file.

In Windows saving the file is usually the only time things get more complicated because Windows can silently add a .txt file extension and you end up with a file named userChrome.css.txt. To avoid this you need to make sure to select "All files" in the dialog to save the file in the text editor using "Save File as".

You need to close (Quit/Exit) and restart Firefox when you create or modify the userChrome.css file.