167177 - systemwide userChrome.css and userContent.css

Status: RESOLVED WONTFIX

(Core :: CSS Parsing and Computation, enhancement, P3)

Description

[Helge Hielscher]

A systemwide userChrome.css (e.g. /usr/lib/mozilla/chrome/userChrome.css) would
make it easier to administrate mozilla on multi user systems(e.g. add
quotecolors for all users).

Comment 1

[Helge Hielscher]

The same applies to the userContent.css. Please split this bug if necessary.

Comment 2

[Boris Zbarsky [:bzbarsky]]

may be a good idea...

Comment 3

[alanjstr]

How about something like the way bookmarks can be done:
user_pref("browser.bookmarks.file", "C:\\folder\\bookmarks.html");

Then all that needs to be dropped in is a user.js to cover both.

Comment 4

[Ben M.]

I think there should also be a global user.js.

Comment 5

[alanjstr]

According to http://www.mozillazine.org/forums/viewtopic.php?t=12745 you can put
user.js in MozillaFirebird\defaults\profile\US

Comment 6

[Neil Jenkins]

alanjstr - that will copy the user.js into any new profile created from that
installation but will not apply it to any existing profiles (ie. its not a
system wide setting). Incidentally, as this folder
(MozillaFirebird\defaults\profile\US) is the template folder for new profiles,
anything in it gets copied to every new profile. So just place userChrome.css
and userContent.css in the chrome folder and they will be copied to every new
profile.

Comment 7

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

I think our experience with system-based extension install indicates that we want to be careful about permissions for such things.  Given that we do have a model for system-wide extension installs (and UI to show users what happened), and extensions can add to user style sheets, I think that should be the recommended way of doing it, and we shouldn't have an additional API for just that.

Comment 8

[Alistair Buxton]

Since extensions can no longer modify browser chrome CSS, this bug should be re-evaluated.

Comment 9

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

I think if we want to provide this sort of functionality, it would belong in the extension API.  Extensions are tied to UI around enabling/disabling, connected to various support mechanisms (e.g., about:support, etc.), and other things.

So if we want such an API it ought to be part of the extension API.  I'm not sure whether it makes sense as the sort of thing we want to support in today's extension API.  But I think that issue should be raised elsewhere (if it's raised at all), and I think this bug should stay as it is.

Comment 10

[Jake]

Users should be able to alter Firefox UI via those files for the whole installation the same way mozilla.cfg is used to config every profile.