When a field is changed on a form, Drupal triggers a 'formUpdated' event on the form element that changed (or trigger a change event on the textarea). See Drupal.behaviors.formUpdated in misc/form.js.

Edit module relies on this event to update the state of it's interface.

#1 pass-events-to-textarea-1895278-1.patch1.63 KBwwalc


wwalc’s picture

The attached patch will work better once the onchange event will be available: http://dev.ckeditor.com/ticket/9794

In the meantime the onchange plugin might be helpful.

wwalc’s picture

Status: Active » Needs review
nod_’s picture

Status: Needs review » Reviewed & tested by the community

works great :) thanks a lot.

wwalc’s picture

Title: WYSIWYG editor should trigger custom Drupal event 'formUpdated' » WYSIWYG editor should allow Drupal to trigger 'formUpdated' event
Status: Reviewed & tested by the community » Fixed
webchick’s picture

Issue tags: +Edit D7 Backport

Just tagging as part of the larger Edit module D7 backport; don't mind me. :D

brycefisherfleig’s picture

Status: Fixed » Needs work

Sadly, this patch seems to connected with my issue #1909150 -- full details on my setup there. If there is any content inside the underlying textarea, then the CKEditor instance will not appear, and I'm left with a regular textarea. I don't really understand what's going wrong, but I keep getting this error message on page load:
"Uncaught TypeError: Object # has no method 'editable' ckeditor.utils.js:93"

Line 92 in sites/all/modules/ckeditor/includes/ckeditor.utils.js references this issue number. I appreciate any help!

wwalc’s picture

Status: Needs work » Fixed

Oops, indeed it could not work with old 3.x, fixed:

brycefisherfleig’s picture

That does seem to fix the error message, but doesn't resolve my other issue. I can't be certain my other issue was caused by this bug -- may well be another module or my custom code. Thanks for the prompt response!!

Automatically closed -- issue fixed for 2 weeks with no activity.