On 02/07/14 22:50, Daniel wrote:
On 02/07/14 21:40, Hartmut Figge wrote:
Daniel:
On 1/07/2014 10:35 PM, Hartmut Figge wrote:

I was showing a way how the problem with the 'light text' could
probably
be solved. Not by altering prefs *g* but by using the file
userContent.css.

Philip then mentioned opacity.

But doesn't the content of userContent.css then get read into prefs.js
and become permanent??

For the user.js that is true.

That's the one!! Even as I was typing my last, I was thinking "No, it's
not userChrome.css, it's ...."
The userContent.css and the userChrome.css
contain CSS rules which affect the appearance of SM itself or its
content. Why not try an example?

In your profile, if you dot not have a directory with the name chrome,
create one. If you have already a userChrome.css in chrome, rename it to
userChrome.css-sav. Copy the attachment of this messages to the
directory chrome. Restart SM and switch to the Mail & Newsgroups Window.

It should be difficult not to notice the effect. :)

To get rid of the example, rename the userChrome.css or delete it and
restart SM again.

Hartmut


userChrome.css



#folderTree {
     background-color: green  !important;
}

Searching for userChrome.css as I type.

Well!! I'm not seeing any green anywhere, so I must have screwed it up!! Time to try a different/lower level in the directory chain.

--
Daniel

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:29.0) Gecko/20100101 Firefox/29.0 SeaMonkey/2.26 Build identifier: 20140415200419
or
User agent: Mozilla/5.0 (X11; Linux x86_64; rv:29.0) Gecko/20100101 SeaMonkey/2.26 Build identifier: 20140408191805
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Reply via email to