Opened 15 years ago

Closed 9 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 dylan)

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 15 years ago by Adam Peller

Owner: changed from James Burke to Ben Lowery

comment:2 Changed 15 years ago by bill

Milestone: 0.91.1

comment:3 Changed 14 years ago by bill

Milestone: 1.11.2

Move all milestone 1.1 tickets to 1.2, except for reopened tickets and tickets opened after 1.1RC1 was released.

comment:4 Changed 14 years ago by dylan

Description: modified (diff)
Milestone: 1.2future

Moving undo/back bugs to future until Ben or someone else has time to tackle them.

comment:5 Changed 10 years ago by ben hockey

Keywords: needsreview added

comment:6 Changed 9 years ago by dylan

Resolution: wontfix
Status: newclosed

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.