Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
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.
Comment | File | Size | Author |
---|---|---|---|
#1 | pass-events-to-textarea-1895278-1.patch | 1.63 KB | wwalc |
Comments
Comment #1
wwalc CreditAttribution: wwalc commentedThe attached patch will work better once the
onchange
event will be available: http://dev.ckeditor.com/ticket/9794In the meantime the onchange plugin might be helpful.
Comment #2
wwalc CreditAttribution: wwalc commentedComment #3
nod_works great :) thanks a lot.
Comment #4
wwalc CreditAttribution: wwalc commentedThanks for reviewing ;)
http://drupalcode.org/project/ckeditor.git/commitdiff/a5eaedb
Comment #5
webchickJust tagging as part of the larger Edit module D7 backport; don't mind me. :D
Comment #6
brycefisherfleig CreditAttribution: brycefisherfleig commentedSadly, 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!
Comment #7
wwalc CreditAttribution: wwalc commentedOops, indeed it could not work with old 3.x, fixed:
http://drupalcode.org/project/ckeditor.git/commitdiff/9308f1e
Comment #8
brycefisherfleig CreditAttribution: brycefisherfleig commentedThat 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!!