RESOLVED WORKSFORME 6692
Certain non-undoable DOM operations can cause unexpected behavior or crashes later on Undo/Redo 
https://bugs.webkit.org/show_bug.cgi?id=6692
Summary Certain non-undoable DOM operations can cause unexpected behavior or crashes ...
Justin Garcia
Reported 2006-01-20 18:29:37 PST
The Undo stack gets hosed by TinyMCE's custom Undo. In "custom-undo" mode, TinyMCE use execCommand(Undo, ...) to implement Undo, it uses setInnerHTML, and our Undo stack isn't bulletproof against arbitrary DOM operations.
Attachments
Add attachment proposed patch, testcase, etc.
Justin Garcia
Comment 1 2006-01-20 18:42:20 PST
I meant to say "In 'custom-undo' mode, TinyMCE DOESN'T use execCommand(Undo, ...)..." in my comments above.
Ryosuke Niwa
Comment 2 2012-04-30 22:43:31 PDT
I haven't seen crashes caused by this bug as long as I've been working on the editing. So I'd assume we've worked out all the kinks in undo/redo by now. Please file more specific bugs and/or re-open this bug if you find specific crashes or unexpected behavior caused by this bug.
Note You need to log in before you can comment on or make changes to this bug.