Bug 6692 - Certain non-undoable DOM operations can cause unexpected behavior or crashes later on Undo/Redo
Summary: Certain non-undoable DOM operations can cause unexpected behavior or crashes ...
Status: RESOLVED WORKSFORME
Alias: None
Product: WebKit
Classification: Unclassified
Component: HTML Editing (show other bugs)
Version: 420+
Hardware: Mac OS X 10.4
: P2 Normal
Assignee: Justin Garcia
URL:
Keywords:
Depends on:
Blocks: 6627
  Show dependency treegraph
 
Reported: 2006-01-20 18:29 PST by Justin Garcia
Modified: 2012-04-30 22:43 PDT (History)
5 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Justin Garcia 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.
Comment 1 Justin Garcia 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.
Comment 2 Ryosuke Niwa 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.