Opened 16 years ago
Closed 14 years ago
#1045 closed defect (wontfix)
dojo.undo.browser breaks in ambiguous situations
| Reported by: | Owned by: | Ben Lowery | |
|---|---|---|---|
| Priority: | high | Milestone: | 1.1 |
| Component: | General | Version: | 0.3 |
| Keywords: | undo dojo.undo.browser history back-button | Cc: | |
| Blocked By: | Blocking: |
Description
Given a page index.html which uses dojo.undo.browser to change urls, if a user visits:
(1) index.html#a (2) index.html#b (3) index.html#c (4) index.html#b
in that order, then presses back three times, the third back will not affect the page.
What happens is that dojo correctly interprets the first back as a movement from (4) to (3), but then misinterprets the second back as a forward (since (2) and (4) are the same url), and assumes we are now at (4). When the user presses back a third time, dojo cannot work out how we reached (1), and thus doesn't call a state handler.
Change History (4)
comment:1 Changed 16 years ago by
| Milestone: | → 0.5 |
|---|
comment:2 Changed 15 years ago by
| Owner: | changed from anonymous to Ben Lowery |
|---|
comment:3 Changed 14 years ago by
| Milestone: | 0.9 → 1.1 |
|---|
comment:4 Changed 14 years ago by
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
Sadly we're limited by the browsers here. They (at least firefox / safari) don't deal with the hash as a history marker in more than one place in a sane manner, so we can't really either. Won't fix for now, unless someone comes up with something brilliant to work around the problem.