font color in TinyMCE window in the backend

[cnisvcs]

It seems like a silly problem and something that should be easily resolveable, but I am not finding any working solution.

My template stylesheet with screen media type determines background color as globally black and font color as white with the following code:

body {
font: normal 0.8em Verdana, Arial, Helvetica, sans-serif;
color: #FFFFFF;
background: #000000 url([[root_url]]/img/bkgdBody1.jpg) no-repeat top center;
}
-- pretty typical

The Content editor with WYSIWYG on shows the text white on white background. Tried to address that by adding:

body {color: black;}
body {color: #000000;}
* {color: #000000;}
html * {color: #000000;}
p {color: #000000;}

with a few other combinations of abovementioned in the 'Additions to stylesheet' field under TinyMCE Advanced tab to no avail. Also tried adding

color: black;
color: #000000;
body {color: #000000;}

in the 'Body tag CSS' field in the same section, same with no result.

Is this a glitch or I am trying wrong things? Anyone has a working solution for this?

I should mention: CMSms 1.9.3 with TinyMCE 2.8.3.

[kasimir]

Black Background: background-color:#00000;

Black font color:#00000;

Kasimir

[Wishbone]

Also, Tiny has a caching issue in 1.9.3.. I had a similar issue where changes to stylesheets weren't showing up. I find that if I log out (not close the window), and log back in, all my settings show up..

I just added:

Code: Select all

body {
background-color: black;
}

to Extensions->Tiny->Advanced->Additions to Stylesheet

Logged out and back in, and my Tiny window is black.

[cnisvcs]

Thank you Kasimir, I just wanted to have the font in black in the backend TinyCME.

Wishbone - you are right on the money! The settings were correct all along. It was the caching issue that prevented them from being applied properly. After I entered the additional styling for TinyCME, I saved them and immediately opened the page content edit mode, never logging out/in in the meantime.

It did cross my mind that caching may have something to do with that, so I cleared the cache (Site Admin -> Global Settings -> Advanced Setup -> Server cache Settings -> Clear), but that obviously affects the front end pages. (Duh)

Also I opened the site backend in another browser, but that was with the primary browser still logged into the admin, so the issue persisted. Interesting.

Thank you so much, Wisbone !!!

[Wishbone]

This is supposed to be fixed in 1.9.4, coming soon.. (This weekend?)