Trane Francks <[email protected]> wrote: > On 8/10/13 4:58 PM +0900, Rob wrote: >> Ralph Fox <[email protected]> wrote: > >>> To control the signature display, follow the instructions at >>> http://kb.mozillazine.org/Signature_display_color >> >> Thanks, that is the article discussing the problem I have. >> >> Unfortunately it only discusses a solution that works "per user". >> What I need is a solution that works "per installation". >> >> Is there an equivalent for userContent.css that can be copied somewhere >> in the program directory and that overrides css for all users of that >> particular installation? > > I'm fairly certain the answer will be no. That said, it's a relatively > simple task to create a script that can be run at user login to check > for the existence of the string in the user userContent.css and add it > if missing.
Sure. But the login script already has become very convoluted due to all the workarounds for problems that are never solved. I prefer solutions that need to be put only in installation scripts for the specific program, not in the script run at every login. It would be reasonable when a solution that is presented "per user" is also available "per installation" (like e.g. the solution for extensions/plugins). Maybe the program could read and add all .css files found in the chrome subdirectory in the installation directory before it reads the userContent.css? Like it does for defaults/pref for .js files. Well, we probably won't be installing 2.20 anyway due to other flaws. We appear to be stuck to 2.14.1 because more and more things that are critical to us are being broken. (e.g. IMAP mail, composer) In the Mozillazine article I found a solution that can be included in the signature itself. At least it solves the problem for the display of our signature in other people's mail should they have upgraded. Of course it creates invalid HTML. <style> is not allowed in <body>. E.g. roundcubemail does not handle it correctly when composing. But should we ever upgrade, at least the mail sent from today will have the signature displayed correctly in that new version. Maybe that is sufficient. _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
