Comments on: Emulating onhashchange without setInterval

By: JavaScript soll Raute in der Url erkennen - Javascript & Ajax @ tutorials.de: Forum, Tutorial, Anleitung, Schulung & Hilfe

Tue, 24 Nov 2009 02:50:04 +0000

[...] JavaScript soll Raute in der Url erkennen Moin, schau mal hier vorbei: http://www.zachleat.com/web/2008/08/…t-setinterval/ __________________ ☀ spread hope ☭ Dieser Beitrag ist Beerware. We [...]

By: Iframe Problem?! - PHP script resource

Iframe Problem?! - PHP script resource — Thu, 10 Sep 2009 13:09:32 +0000

[...] [...]

By: Zach Leatherman

Zach Leatherman — Thu, 09 Jul 2009 00:43:08 +0000

This approach shouldn’t be needed in IE8, as it has the onhashchange event. See the article for a link.

Let me know if you’re seeing problems with it!

Thanks for the kind words,
Zach

By: James Close

James Close — Mon, 06 Jul 2009 10:23:15 +0000

Hi Zach
I really liked your approach here and have been using it successfully on a site for the past few months. I have noticed that it does not seem to work with IE8 (even in compatibility mode). The IFrame appears to be reset when navigating back through history. Do you have any thoughts on this? Thanks again for your great work on this. JC

By: Recent Links Tagged With "yui" - JabberTags

Recent Links Tagged With "yui" - JabberTags — Wed, 15 Oct 2008 03:19:37 +0000

[...] public links >> yui Yui Aragaki, Bomb TV photobook Saved by parcifal on Mon 13-10-2008 Emulating onhashchange without setInterval Saved by Gorillazfan1230 on Mon 13-10-2008 Parfait Chocolat second brew re-order review Saved by [...]

By: Nathan Hammond

Nathan Hammond — Wed, 08 Oct 2008 18:08:36 +0000

Hey Zach, me again. I wanted to point you in the direction of some of the work being done on this topic: HTML 5 and History Management Also, I alluded to doing some work myself, that is now up at: JSSM It is based on the approach taken by RSH, and the two will be merged to be the same library come the respective 1.0 versions to prevent history manager proliferation. Also, I noted somewhere you discussed using jQuery's data method to store information. The reason history managers have adopted the form-based approach is because it allows us to restore the session state after leaving the site (relying upon browsers automatically repopulating the form fields). The jQuery data element is garbage collected once the current document element changes and so if you navigate away you lose all associated information.

By: fishing for water » Ajax and the Back Button (Ben Dillard)

fishing for water » Ajax and the Back Button (Ben Dillard) — Wed, 01 Oct 2008 18:12:35 +0000

[...] – Zach Leatherman has a CSS-based approach that doesn’t use setInterval [...]

By: Nathan Hammond

Nathan Hammond — Wed, 27 Aug 2008 23:39:59 +0000

Zach,
I’m intrigued by this. So simple and elegant that it is kinda scary. I’d love to see continued development down this path to try and work around the limitations as I see them:
1. No bookmarking ability. That could get especially tricky in browsers that register events on hash change, like Firefox. Cause and effect get all messed up.
2. Safari. *sigh* A-grade browsers. Bah.
3. Client-side style sheets. Text size changes. Zoom changes.

I’m in the process of writing a history manager right now (timer-based, supports IE8’s default event), so I’ll stay tuned.

By: Zach Leatherman

Zach Leatherman — Fri, 22 Aug 2008 18:51:20 +0000

Look for a fix to the “resize text” problem later this evening. I’m going to wait until I’m not on the employer dime to work on that.

By: Ajaxian » Emulating onhashchange without setInterval

Ajaxian » Emulating onhashchange without setInterval — Fri, 22 Aug 2008 12:21:06 +0000

[...] Leatherman has revisited the problem and has another solution that doesn’t require setInterval to check on the [...]