Opened 9 years ago
Closed 9 years ago
#11078 closed defect (fixed)
dijit.Editor: Chrome timing issue with this.savedContent and customUndo
| 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
Due to chrome's speed and its async behavior, the startup of editor does not properly save off the initial content (which is used as step 0 of customUndo). This makes undo work a little oddly in chrome, in that going back far enough blanks the editor completely.
This should be a trivial fix, working on it now.
Note: See
TracTickets for help on using
tickets.
(In [22045]) Fixing timing issue in Chrome with regards to forwrd/back button timing of creating customUndo array. \!strict fixes #11078