Opened 14 years ago
Closed 7 years ago
#2361 closed defect (wontfix)
dojo.undo.browser: Consider making convenience methods for getting/setting current state.
| Reported by: | James Burke | Owned by: | Ben Lowery |
|---|---|---|---|
| Priority: | high | Milestone: | future |
| Component: | General | Version: | 0.4.1 |
| Keywords: | needsreview | Cc: | |
| Blocked By: | Blocking: |
Description (last modified by )
Something like dojo.undo.browser.getCurrentState() and dojo.undo.browser.setCurrentState() to get the state object in the this.historyStack[this.historyStack.length - 1].
There are times when an application might want to update the current state without adding a new state to the stack (the state change does not warrant a "page change").
Change History (6)
comment:1 Changed 13 years ago by
| Owner: | changed from James Burke to Ben Lowery |
|---|
comment:2 Changed 13 years ago by
| Milestone: | 0.9 → 1.1 |
|---|
comment:3 Changed 12 years ago by
| Milestone: | 1.1 → 1.2 |
|---|
comment:4 Changed 12 years ago by
| Description: | modified (diff) |
|---|---|
| Milestone: | 1.2 → future |
Moving undo/back bugs to future until Ben or someone else has time to tackle them.
comment:5 Changed 8 years ago by
| Keywords: | needsreview added |
|---|
comment:6 Changed 7 years ago by
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
dojo.undo isn't a thing in modern dojo, dojo.back is deprecated, and between dojo/hash and dojo/router we think this is covered, so closing as wontfix.
Note: See
TracTickets for help on using
tickets.
Move all milestone 1.1 tickets to 1.2, except for reopened tickets and tickets opened after 1.1RC1 was released.