Emulating onhashchange without setInterval
location.hash? Sure, you can tell when you’re modifying the hash yourself, but what if the user hits the back/forward button?
YUI’s History component and Really Simple History both use setInterval with an internal variable to compare and find changes. But this isn’t really an optimal solution. As proper front end engineers, we should avoid timeouts as much as possible. Internet Explorer 8 will have an onhashchange event that clients will be able to subscribe to. That will be nice. But surely, a cross browser solution without the use of setInterval exists.
Look, a cross browser solution without the use of setInterval:
- On initialization, we load an iframe onto the page that is positioned absolutely at -500px,-500px so the user can’t see it. It is a skeleton page that only needs cross browser code to add an “
onscroll” event, and to be able to calculate the scrolled position of the iframe itself. For my example, I use jQuery and the dimensions plugin to accomplish this, but it could easily be trimmed down to only the bare essentials (or ported to a different library).
- To add an AJAX history entry into the browser’s history under an assigned hash string, we first add a
<a name="hashString">hashString</a>to the
<body>tag of the iframe. Using css to increase the size of the a tag proportional to the iframe’s height, we can guarantee scrolling will happen.
- Then, we change the
location.hashof the iframe to point to that
<a>tag. This will scroll the iframe to the content, and create a new entry in the browser’s
- Inside the iframe, we have our
onscrollevent that fires when the scrolling in the previous step took place. (Minor IE-related workaround: The browser’s
historyobject is changed, but the hash property doesn’t when attempting to read it later. Instead, we find the
<a>that matches up with the scrollY/pageOffsetY property inside of the iframe, and retrieve the matching hash from the
The nice thing about this approach is that you don’t even need a history manager anymore. This little iframe will do all of your dirty work for you. And it will even maintain your history alongside any other iframe browsing on the page.
- Can serve as back button support and full AJAX history manager.
- Cross browser: Tested in FF3, IE7, IE6, Opera 9.5, (not Safari — see below)
- No bookmarking support. We aren’t changing the top hash, we’re changing the iframe hash, so these aren’t bookmarkable.
Update: Given time for more rigorous testing, it doesn’t look like Safari supports this approach. So, until WebKit fixes #9166, we’ll have to stick to timers in Safari. A more pragmatic programmer than I might hack around this approach by exploiting #19202, but that certainly wouldn’t be a long term solution. I’ve also updated the test page above, at Dean Edwards humble request, to support dynamic client size text size changes.
Zach Leatherman Disqus22 Aug 2008
Nathan Hammond Disqus28 Aug 2008
Nathan Hammond Disqus08 Oct 2008
James Close Disqus06 Jul 2009
Zach Leatherman Disqus09 Jul 2009