Ajax requests into browser history
Added by Henrik Ammer almost 15 years ago
I find it a bit annoying when using an application with Ajax calls that does not use a History manager on the requests that changes the contents since if I leave a page that has done something through Ajax requests and hit the back button, the info is not that of what I left the page with.
There are some history managers out there, I found reallysimplehistory that needs no framework since a good history manager for the prototype framework seems a bit scarce.
I found this but it's from 2007 so it might not work with the current prototype version.
Google gave me a link, http://www.prototypextensions.com/history, that sounded promising but the website does not respond :(.
Another one is swfaddress.
Should this be a feature or not?
Replies (2)
RE: Ajax requests into browser history - Added by Anonymous over 14 years ago
I agree -- it's aggravating to page through issue listings, visit one of the issues, then hit the Back button and wind up on page 1 of the listing again. I'm about to deploy Redmine at my company and I suspect people are going to be complaining about this.
This seems to be issue #3494. If no one's going to fix this in the near term, is there a way to work around it by disabling AJAX for issue-list updates?
RE: Ajax requests into browser history - Added by Henrik Ammer over 14 years ago
That issue (#3494) is close but not entirely what I was thinking about. Think of this case:
You go and update a ticket with a new note and save. You then go to edit that text so you hit the edit button on the note but after re-reading the text you realize it's ok and you want to hit the back button (or actually mousebutton for me on my six button mouse) and want to go back seeing the issue with your note not in edit mode. You wind up on the previous page (for instance issueslist).
The same goes for this reply. If I would hit the back button now it would return to the login page which was is my previous page in the history.