Hi all
I am in a big confusion at this moment with the way the WYSIWYG is behaving.
I am currently doing several testing using our new templates which looks great, but I have stuck in the deep end and finding it hard to get out of it.
Basic problem is when editing a homepage, the background image repeats over the whole area, making the text hard to see and edit.
Unfortunately the css put the background image in there (custom.css), theoretically it should be able to take it out, but haven’t found a concrete fix for it.
Putting override rules in ‘simple_edit.css’ and ‘editing.css’, but neither worked. Finally tried using the ELSE to hide the custom.css, again hit the brick wall. 
<MySource_AREA id_name="simple_edit" design_area="show_if">
<MySource_SET name="condition" value="simple_edit_mode" />
<MySource_THEN>
<link rel="stylesheet" type="text/css" href="mysource_files/editing.css" media="screen" />
<link rel="stylesheet" type="text/css" href="http://xxx.xxx.xxx.xxx/xxxxx-xxxx/07/styles/simple_edit.css" media="screen, projection" />
</MySource_THEN>
Has anyone out there done a similar or better way which works well for them? :blink:
Cheers :lol:
Use the CSS File asset instead of a static CSS file – then it will not be imported into the WYSIWYG.
Have long ago considered and discarded the CSS asset option because it introduced other issues.
Obviously, the wysiwyg recognises some css - limited and inconsistent, but that is fine - a wysiwyg is not a browser. What I'm completely flummoxed by is that having recognised one style delivered by a linked style sheet, I can't get it to recognise another overriding style. Is there any information on where it gets its style information from? precedence, specificity, syntax? what gets recognised and what gets ignored? I've tried following the trail of css through the divs and iframes, but end up going in circles.
Perhaps we should (also) look at what issues it introduced?