Update: There is now the HTML5 History API (pushState, popState) which deprecates the HTML4 hashchange functionality. History.js provides cross-browser compatibility and an optional hashchange fallback for HTML4 browsers. The answer for this question will be more or less the same as my answers for these questions: How to show Ajax requests in URL? How does … Read more
You can detect if the browser supports the event by: if (“onhashchange” in window) { //… } See also: Detecting event support without browser sniffing Emulating onhashchange without setInterval window.onhashchange
Google Custom Search Engines use a timer to check the hash against a previous value, whilst the child iframe on a seperate domain updates the parent’s location hash to contain the size of the iframe document’s body. When the timer catches the change, the parent can resize the iframe to match that of the body … Read more
For the demo linked in your question, achieving that functionality is actually really simple – as it doesn’t use any AJAX at all (when you start to add AJAX to the mix, it get’s more difficult – explained later). To achieve that functionality you would; upgrade your links to use hashes, then bind into the … Read more
The answers here are all quite old. In the HTML5 world, you should the use onpopstate event. window.onpopstate = function(event) { alert(“location: ” + document.location + “, state: ” + JSON.stringify(event.state)); }; Or: window.addEventListener(‘popstate’, function(event) { alert(“location: ” + document.location + “, state: ” + JSON.stringify(event.state)); }); The latter snippet allows multiple event handlers to … Read more
If you want it to work in browsers that don’t support history.pushState and history.popState yet, the “old” way is to set the fragment identifier, which won’t cause a page reload. The basic idea is to set the window.location.hash property to a value that contains whatever state information you need, then either use the window.onhashchange event, … Read more
The only way to really do this (and is how the ‘reallysimplehistory’ does this), is by setting an interval that keeps checking the current hash, and comparing it against what it was before, we do this and let subscribers subscribe to a changed event that we fire if the hash changes.. its not perfect but … Read more