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?
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
Re: What NEEDS to go in contentsCss