Experiences with Javascript History Frameworks

Question

I\'m seeking a javascript history framework to handle navigation inside a page when the user selects multiple options which change the page behaviour.

There are mult

Answer 1

I had the similar problem a while ago building a flash only site. We tried:

• Really Simple History (which had some problems in combination of safari and flash)
• ExtJS which has a history component which worked great for us. (Demo) [Beside we have used this framework already for other projects.]

Answer 2

jQuery History is my preferred choice. It can be found here: http://www.balupton.com/projects/jquery-history/ Provide cross browser support, binding to hashes, overloading hashes, all the rest.

There is also an Ajax extension for it called jQuery Ajaxy, allowing it to easily upgrade your webpage into a proper Ajax application without need for server side changes and remaining SEO and JS-Disabled friendly: http://www.balupton.com/projects/jquery-ajaxy/

Overall they are both well documented, supported and feature rich. They've also won a bounty question here How to show Ajax requests in URL?

Answer 3

Dial.js is a JavaScript browser history framework designed to provide some of the features of a full-fledged MVC framework with jQuery and History.js for single-page applications (SPAs).

Answer 4

Maybe this question is usefull to you. In the question I linked to a testpage, where location.hash is used to keep track of the history. I am currently using this method in a testsite and experienced problems with Opera (truncates a location.hash value at the question mark, you'll have to use: location.href.split(/#/)[1]) and of course IE (needs an iframe). In IE with iframe the history is saved for the current session only. If you load another page in the same window/tab and use the back button to go back to the AJAX page, the previous history is lost. It's not that big a deal for me, but may be annoying. I understood that IE8s history should behave like expected with location.hash, it even should have a hashchange handler.

I think most of the frameworks use the same technique (monitoring location.hash for changes, using an iframe for IE). I didn't want to use a framework, because I'm using my own home brew small framework and regular frameworks contain too much functionallity I'll never use.