below is the changes I did in the '_samples\stylesheetparser.html' file in order to activate fullPage. I tried with Firefox 4 and is not working for me. I also tried with custom config file and had the same result.
CKEDITOR.replace( 'editor1' , { extraPlugins : 'stylesheetparser', /* * Stylesheet for the contents. */ fullPage : true,
contentsCss : 'assets/parsesample.css', /* * Do not load the default Styles configuration. */ stylesSet : [] });
I have a unique situation where I'm editing full page html AND I need to have certain css classes recognized using the contentCss setting. This is to provide a special highlighting of spans with the class so they stand out in the editor because double clicking them triggers a specific plugin. However, the edited HTML doesn't have a <link> tag referenceing the css file nor should it have that <link> when saved. I am upgrading from 3.6.2 (where this worked fine) to 4.2.1. I can add code to my system that would force the <link> tag into the HTML before loading the editor and strip it back out when saving but I'd really prefer to not alter my code that much when the cause is a change in this tool's behavior. Is there a work around/fix or is my only option to modify my code?
Re: 'stylesheetparser' not working when config.fullPage = tr
Re: 'stylesheetparser' not working when config.fullPage = tr
CKEDITOR.replace( 'editor1' ,
{
extraPlugins : 'stylesheetparser',
/*
* Stylesheet for the contents.
*/
fullPage : true,
contentsCss : 'assets/parsesample.css',
/*
* Do not load the default Styles configuration.
*/
stylesSet : []
});
Re: 'stylesheetparser' not working when config.fullPage = tr
Re: 'stylesheetparser' not working when config.fullPage = tr
Re: 'stylesheetparser' not working when config.fullPage = tr
Need BOTH contentsCss AND fullPage = false
I have a unique situation where I'm editing full page html AND I need to have certain css classes recognized using the contentCss setting. This is to provide a special highlighting of spans with the class so they stand out in the editor because double clicking them triggers a specific plugin. However, the edited HTML doesn't have a <link> tag referenceing the css file nor should it have that <link> when saved. I am upgrading from 3.6.2 (where this worked fine) to 4.2.1. I can add code to my system that would force the <link> tag into the HTML before loading the editor and strip it back out when saving but I'd really prefer to not alter my code that much when the cause is a change in this tool's behavior. Is there a work around/fix or is my only option to modify my code?