What steps will reproduce the problem?
Set up the historyManager so that it submits some random historyData with
each url that is added with dhtmlHistory.add(). Now go to some URL A, the
go to some URL B and then go to the first URL A. Now the historyData from
the first time URL A was visited will be overwritten by the historyData
from the second time URL A was visited.
What is the expected output? What do you see instead?
I would expect the data that is associated with each dhtmlHistory.add()
call to not be overwritten if variying data is sent with the same url (as
in the scenario described above). The are cases where the url is not enough
as the key for the historyData.
What version of the product are you using? On what operating system?
RSH0.6FINAL. The lib is served from a LAMP server and the problem occurs
regardless of browser.
Please provide any additional information below.
I guess the problem is in using the url as key for saving the historyData.
Something else is needed to associate different data with the same url. The
problem is I can't quite come up with what extra data to use for this
identifier. Obviously it has to be something that is present when the user
changes his location in the history but it must be unique for each url
(even identical urls).
Original issue reported on code.google.com by kaj...@gmail.com on 29 Apr 2008 at 9:16
Original issue reported on code.google.com by
kaj...@gmail.comon 29 Apr 2008 at 9:16