Opened 10 years ago

Closed 10 years ago

#11079 closed defect (fixed)

CustomUndo is a bit flakey in W3C range browsers (FF, Chrome, etc)

Reported by: Jared Jurkiewicz Owned by: Jared Jurkiewicz
Priority: high Milestone: 1.5
Component: Editor Version: 1.5.0b1
Keywords: Cc:
Blocked By: Blocking:

Description

CustomUndo? is a bit flakey in W3C range browsers (FF, Chrome, etc)

The way it handles bookmarking needs a bit of work. There are a few things that we need to handle a bit better to make it more robust. This ticket is a good point for implementing the fixes.

Change History (3)

comment:1 Changed 10 years ago by Jared Jurkiewicz

(In [22046]) First patch to customUndo/w3C range code to fix initial state errors with undo. (Exceptions were thrown when reverting to initial browser state WRT the selection restore. \!strict refs #11079

comment:2 Changed 10 years ago by Jared Jurkiewicz

(In [22047]) Updating view source to trigger begin/end enditing, which in customUndo saves state. \!strict refs #11079

comment:3 Changed 10 years ago by Jared Jurkiewicz

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.