Hi everybody.
There's a little question.
If I set the config.baseHref option to the root path of my home page (which is different from the ckeditor page), I need to set config.contentCss to the path relative to the baseHref.
So if without setting baseHref the path was (for example) "../style/style.css", now I need to set it to "style/style.css", to see the content of the editor in the same way I see the public page.
But the baseHref option was not considered by the pulldown menus (Format, Style and Size), so the preview of the style I'm choosing inside the menu is not correct and is shown w/o considering the css rules (with the standard style, black Times New Roman), while it can't find the style.css file. If I turn the config.contentCss to the path relative to the page with the editor ("../style/style.css" in the example above), the menus work fine, but obviously the main window stops working correctly.
The only way to make all working correctly is to set the contentCss to the full path including http and domain.
Since it works there isn't a real trouble, but I feel this is a little bug to fix, or, if not, someone can tell me the reason of this behavior?
P.S. I'm not English speaking, so forgive me for the mistakes i've made.
Wed, 04/28/2010 - 11:47
#1

Re: config.baseHref and config.contentCss