[Wicket-develop] another problem with the pagemap access stack..

[Johan Compagner]

Hi,

Now we have pretty much solved the new tab/window issue by auto generation pagemaps.
There is another problem with the access stack a pagemap does have.

when i have this access stack:

Page1, Page2, Page3, Page4

and i go to Page2 and press refresh....
Then wicket will throw away Page3 and Page4 because it sees that we touch Page2..
But with a refresh the location (url) doesn't change so the history doesn't change so you still can go forward.

Is this refresh the only thing that doesn't invalidate the history?
Is there an usecase where i can click on something that also keeps the current location and therefor the history
is not touched?

Because i guess if it is only a refresh we can test this and don't drop the pages above it. But if there are other
possibilities we have a bit bigger problem.

johan