wysiwyg body background

On the whole we have found that clients tend to prefer editing their pages in the wysiwg editor, but this is causing a problem of it's own for some sites.

The wysiwyg seems to use the body tags background for the background of the editing which means quite often they are trying to read text over a color or pattern that the content doesn't have. In one instance the content area on the site is white but the background to the body is the same green as the a tags and therefore you can't see the a tags in the wysiwyg.

I thought I would ask if anyone else come across this problem and if so worked out a solution before I pull the code apart and try to come up with a work around.

Jai

On the whole we have found that clients tend to prefer editing their pages in the wysiwg editor, but this is causing a problem of it's own for some sites. The wysiwyg seems to use the body tags background for the background of the editing which means quite often they are trying to read text over a color or pattern that the content doesn't have. In one instance the content area on the site is white but the background to the body is the same green as the a tags and therefore you can't see the a tags in the wysiwyg. I thought I would ask if anyone else come across this problem and if so worked out a solution before I pull the code apart and try to come up with a work around. Jai

Create a xinha.css stylesheet in a plugin or theme and xinha will pick this up and you can use it to override the look of everything in the xinha body area.

Create a xinha.css stylesheet in a plugin or theme and xinha will pick this up and you can use it to override the look of everything in the xinha body area.

this can also be a way to get styles in/out of xinha - because xinha only picks up the content in it's own shell, anything styled specifically, for example #content p, will be ignored in xinha, unless you put it in xinha.css.

This means you styles you don't want showing up for users can easily be hidden by making them more specific (I've tried to do this with a lot of the admin styles like div.contactform which were showing up in xinha and confusing users, by making them tag specific eg: form.contactform).

Caching can make it slightly painful to get any changes to xinha.css to actually show up, so, as with ie_style.css, it's easiest to navigate to the css file directly and force refresh in order to update the cached copy

this can also be a way to get styles in/out of xinha - because xinha only picks up the content in it's own shell, anything styled specifically, for example #content p, will be ignored in xinha, unless you put it in xinha.css. This means you styles you don't want showing up for users can easily be hidden by making them more specific (I've tried to do this with a lot of the admin styles like div.contactform which were showing up in xinha and confusing users, by making them tag specific eg: form.contactform). Caching can make it slightly painful to get any changes to xinha.css to actually show up, so, as with ie_style.css, it's easiest to navigate to the css file directly and force refresh in order to update the cached copy

Awesome guys. Thanks heaps.

Awesome guys. Thanks heaps.