Hi everyone,
I am using CKeditor in connection with IBM Domino Server 9 (which has it integrated and bundled in version cke_version=3.6.6.1, cke_revision=20130114-1730) and I am trying to find a convenient (for us) way to prevent autogrowth of the editor in our forms.
What I am doing currently is attaching to the 'autoGrow' event and simply canceling it by calling ev.cancel().
Now this works for all browser I've tried this in (Firefox, IE, Chrome and Safari (win)) but NOT for Safari on iPad.
I've reassured that ev.cancel() is called (by inserting alerts into my code) but the browser (or whatever) simply seems to ignore it.
Might this be a bug in CKEditor or am I doing something completely wrong?
Kind regards
Johannes
PS: Code Snippet
CKEDITOR.on('instanceReady', setMainFont);
...
function setMainFont(ev)
{
...
ev.editor.on('autoGrow', function(e) {
e.cancel();
});
...
}
If you do not want to use the
If you do not want to use the AutoGrow feature, you can simply disable the autogrow plugin. See here: http://docs.ckeditor.com/#!/guide/dev_howtos_basic_configuration-section-3
Documentation Manager, CKSource
See CKEditor 5 docs, CKEditor 4 docs, CKEditor 3 docs, CKFinder 3 docs, CKFinder 2 docs for help.
Visit the new CKEditor SDK for samples showcasing editor features to try out and download!
Thank you, Anna, for your
Thank you, Anna, for your response.
I am aware of this possibility but this would affect the whole of the Domino Server and not just our application. We would like to avoid letting people do global changes to their server (perhaps other applications rely on autogrow?) when they are using our databases.
Any other hints?
Kind regards
Johannes
create a custom config .js file
Hi Johannes,
You can use a custom configuration file installed into the .nsf as a javascript file. We use the one supplied by IBM as a starting point and then modified it to meet our needs. The original file is at 'data/domino/html/ckeditor/config.js'. To get the editor to use this add a dojo attribute to the RTE control with a name of customConfig and a computed value to point to your config file (i.e. "/"+@DbName()[1]+"/CKECustomConfig.js?open"). You may need to keep your custom config file in sync with any changes made by IBM to the default one as we did when upgrading to D9.
Rich