Log in or register to post comments
Last post
What NEEDS to go in contentsCss
If the page hosting CKEDITOR includes the styles that will be present when the edited content is later presented in situ, should it be necessary to specify contentsCss? I did some experiments with that when I first started using ckeditor a year or so ago, but I think my conclusions were tainted by some errors outside the test. Now I've organized the host document around segregating those styles in a file supplied to contentsCss but I'm thinking maybe I never needed to do that in the first place.

Does one gain anything by running the styles through contentsCss (or lose something by not doing so) or is it just a way to provide styles that aren't otherwise accessible because they aren't present in the host document?
Re: What NEEDS to go in contentsCss
The editor uses an iframe for the edited content, so you should put in contentsCss a style sheet that matches the styles of the final page so the user can check that the colors, fonts, borders, whatever while editing instead of requiring him to edit with basic black-and-white and then check the output page to verify that it looks as he wanted.
Re: What NEEDS to go in contentsCss
OK, I think I get it now. So none of the host document's styles would otherwise have effect in the editor, since it's running in an iframe.