The solution I have is to implement all things in javascript: just setup a timer, if in that period, no user typing, then that marks the end of a typing action.

In my custom Editor (subclass of Editor2) I have commands that know how to undo themselves. I store them onto my javascript undo stack. I also have some editor2commands that call on the browser to perform operations, as well as to undo them. I’ve been pushing all commands onto my stack and everything seems to work fine. However, I am having trouble with events that don’t go through the Editor2 such as the user typing or deleting text in the editor. While i know i can capture key events, it is difficult to know which key events are grouped into a single undo transaction by the browser. So i was wondering if you had any ideas as to how i can figure out when a command gets pushed onto the undo stack of the browser…that way i can at least add some stub commands to my local undo stack and call on the browser to undo as i pop them off my stack. Or if not, any other ideas?

thanks a bunch,
-R