Based on what we talked about I went ahead and added the change event to the editor.
Added a change event to the editor.
I was looking into this as well. I think this needs a bit more love :) I'm travelling today so I won't be able to complete it, but I was thinking about caching the old version and actually comparing it with the current one before triggering change. this should prevent multiple fake triggers and preventing events that don't change content
I understand the need to make it as accurate as possible. I am worried about holding onto the old value though. If there are a couple of images in the editor then it could be multiple MBs being stored and compared. That could be slow and consume a decent chunk of memory.
hm... you're right. perhaps a checksum then
How to use this to catch changes?
For now i use this
MutationObserver = window.MutationObserver || window.WebKitMutationObserver
observer = new MutationObserver (mutations, observer) ->
scope.data = editor.html()
Hi, I'm trying to use bootstrap wysiwyg as a "local" offline editor. I'm currently trying to make use of garlic.js to get the info in the editor persistent but no luck yet. Any ideas?
how can i bind and use chane event?