Hopefully I'm responding in the right way. Using the mailinglist is rather new to me :-). So apologies if I do it the wrong way.
Date: Sat, 11 Dec 2010 23:40:13 +0530 > From: Kaushik Chakraborty <[email protected]> > > If you're open to HTML5 then you can use LocalStorage APIs to save your > state. Again this depends on the amount of rework you've to do. > Thanks for the suggestion. I´m not in favor of using the LocalStorage APIs, because it removes several use cases for which the hash parameter is useful. It removes support for sharing the URL between users and using the navigation buttons of the browser. Besides this, I also need to support IE7, which doesn't have LocalStorage support. > From: Ryan Grove <[email protected]> > > That's definitely not normal. There's most likely something else going > on in your application -- perhaps an onhashchange subscriber (or > poller) -- which causes this delay when the hash changes. I've worked > with IE8's location hash and onhashchange event extensively and have > never seen a performance issue like this. > As far as I know the hash is only being used for setting the current location within the web application. Later on support will be added for the hashchange event to support the navigation buttons of the browser. > > I recommend creating a reduced test case and trying to reproduce the > problem. Start fresh with only the code that changes the hash, and see > if the problem still exists. If not, gradually start layering more > code on until the problem surfaces. This should help you narrow down > the source of the problem. > > - Ryan > That's going to be tough and will require quite some work. The javascript files together are about 2 to 3 mb.... I think it will take some time to figure this one out. Thanks guys, Sander
_______________________________________________ JSMentors mailing list [email protected] http://jsmentors.com/mailman/listinfo/jsmentors_jsmentors.com List Archive: http://jsmentors.com/pipermail/jsmentors_jsmentors.com/
