Opened 9 years ago

Last modified 9 years ago

#12969 confirmed Bug

SCAYT plugin stops working after setData is called with "Div Editing Area" plugin

Reported by: Jonathan Owned by:
Priority: Normal Milestone:
Component: General Version: 4.0
Keywords: Cc:


The SCAYT plugin does not re-initialize itself after setData is called when using the divarea plugin. Based on the comment in the code it looks like this was a bug for the inline editing mode but was never addressed for the divarea plugin.

From the SCAYT plugin js:

		//#9439 after SetData method fires contentDom event and SCAYT create additional instanse
		// This way we should destroy SCAYT on setData event when contenteditable Iframe was re-created
		editor.on('setData', function() {

			// in inline mode SetData does not fire contentDom event
			if(editor.elementMode == CKEDITOR.ELEMENT_MODE_INLINE) {
		}, this, null, 50);

Here scaytDestroy is called. However, the contentDom event doesn't fire with setData with the divarea plugin and since elementMode is not ELEMENT_MODE_INLINE, contentDomtHandler doesn't get called to reinitialize the plugin.

Change History (1)

comment:1 Changed 9 years ago by Jakub Ś

Status: newconfirmed

Problem can be reproduced from CKEditor 4.0 in all browsers.

Note: See TracTickets for help on using tickets.
© 2003 – 2022, CKSource sp. z o.o. sp.k. All rights reserved. | Terms of use | Privacy policy