Opened 9 years ago
Closed 9 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 9 years ago by
comment:2 Changed 9 years ago by
comment:3 Changed 9 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
(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