We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

A plug-in system to manage userchrome.css changes?

I can't find any mention of the development of a system to manage changes to userchrome.css. Is any such thing planned?

It would be really useful to have a management system for edits to userchrome.css that downloads the edits from trusted developers, installs them, including customization to a user's existing installation, with a couple of clicks, checks for conflicts, automatically updates 'change sets', or whatever they end up being called, when necessary, offers automatic detection of inappropriate behavior and safe-mode removal of bad entries, and otherwise behaves like an interface appropriate for the general public.

Because I have about twenty other problems, of which I already know the answer is "go edit userchrome.css by hand, and integrate multiple changes from multiple sources by hand, and don't forget to read the full documentation of what css does to the browser first."

I can't find any mention of the development of a system to manage changes to userchrome.css. Is any such thing planned? It would be really useful to have a management system for edits to userchrome.css that downloads the edits from trusted developers, installs them, including customization to a user's existing installation, with a couple of clicks, checks for conflicts, automatically updates 'change sets', or whatever they end up being called, when necessary, offers automatic detection of inappropriate behavior and safe-mode removal of bad entries, and otherwise behaves like an interface appropriate for the general public. Because I have about twenty other problems, of which I already know the answer is "go edit userchrome.css by hand, and integrate multiple changes from multiple sources by hand, and don't forget to read the full documentation of what css does to the browser first."

All Replies (3)

Support Volunteers have no idea. I guess it would be, have not had time to play with mine yet. Got any good code sites, pvt message if do. ?

To submit suggestions for new or changed features, may I suggest: Feedback: https://qsurvey.mozilla.com/s3/FirefoxInput/

Please let us know if this solved your issue or if need further assistance.

MyTempAccount said

I can't find any mention of the development of a system to manage changes to userchrome.css. Is any such thing planned? It would be really useful to have a management system for edits to userchrome.css that downloads the edits from trusted developers, installs them, including customization to a user's existing installation, with a couple of clicks, checks for conflicts, automatically updates 'change sets', or whatever they end up being called, when necessary, offers automatic detection of inappropriate behavior and safe-mode removal of bad entries, and otherwise behaves like an interface appropriate for the general public. Because I have about twenty other problems, of which I already know the answer is "go edit userchrome.css by hand, and integrate multiple changes from multiple sources by hand, and don't forget to read the full documentation of what css does to the browser first."

Discussion of userChrome.css and further development shouldn't be done in this forum. Please see your Private Message button at the top of this page for more information that I sent to you via a PM.

In the old days, the Stylish extension was a convenient way to apply custom style rules to Firefox's user interface. Each "user style" or "style recipe" could be enabled/disabled individually in real time. Very convenient, although you still could seriously mess up the UI.

Extensions no longer have those abilities, but the developers are working on a Theming API that extensions can use to make "safe" changes to the interface. It is unclear how far that effort might go in allowing other more adventurous changes users like. Since this is all very speculative, I agree it's not within the mission of the support forum.