Fired when location.hash changes.  In browsers that support it, the native window.onhashchange event is used (IE8, FF3.6), otherwise a polling loop is initialized, running every jQuery.hashchangeDelay milliseconds to see if the hash has changed.  In IE 6 and 7, a hidden Iframe is created to allow the back button and hash-based history to work.

Usage

$(window).bind( 'hashchange', function(e) {
+
hashchange event
Fired when location.hash changes.  In browsers that support it, the native HTML5 window.onhashchange event is used (IE8, FF3.6), otherwise a polling loop is initialized, running every jQuery.hashchangeDelay milliseconds to see if the hash has changed.  In IE 6 and 7, a hidden Iframe is created to allow the back button and hash-based history to work.
Usage
$(window).bind( 'hashchange', function(e) {
   var hash = location.hash;
   ...
-});
Additional Notes
The polling loop and Iframe are not created until at least one callback is actually bound to ‘hashchange’.
If you need the bound callback(s) to execute immediately, in cases where the page ‘state’ exists on page load (via bookmark or page refresh, for example) use $(window).trigger( ‘hashchange’ );
The event can be bound before DOM ready, but since it won’t be usable before then in IE6/7 (due to the necessary Iframe), recommended usage is to bind it inside a $(document).ready() callback.
+});

Additional Notes

• The polling loop and Iframe are not created until at least one callback is actually bound to ‘hashchange’.
• If you need the bound callback(s) to execute immediately, in cases where the page ‘state’ exists on page load (via bookmark or page refresh, for example) use $(window).trigger( ‘hashchange’ );
• The event can be bound before DOM ready, but since it won’t be usable before then in IE6/7 (due to the necessary Iframe), recommended usage is to bind it inside a DOM ready callback.