How does Gmail handle back/forward in rich JavaScript?

前端 未结 2 944
盖世英雄少女心
盖世英雄少女心 2020-12-05 12:38

Gmail seems to have some clever way of handling the back/forward buttons in a rich JS application.

In my organisation we trialled the jQuery history plugin. The plug

相关标签:
2条回答
  • 2020-12-05 12:50

    You might want to check this previous question :

    Is there a way to catch the back button event in javascript?

    It seems like the way it's done in jQuery is the only way to do it because that's what YUI is doing too :

    http://developer.yahoo.com/yui/history/

    0 讨论(0)
  • 2020-12-05 13:00

    Perhaps you are talking about the jQuery History plugin here: http://www.balupton.com/projects/jquery-history Which has been used in many production quality sites; one of my favourites is http://wbhomes.com.au/

    If so, it uses a 200ms test for older generation browsers which do not implement the onhashchange event natively. Without that event implemented natively, you have to workaround it's functionality by using a interval change - there just isn't any other way to my knowledge. Fortunately the latest versions of all the major browsers now support the onhashchange event natively, so this check is no longer needed.

    But alas, let's go into what what that 200ms interval check does. If they are on IE6 or 7, it will check the state of an iframe (as in those browsers a iframe is required to emulate the back and forward buttons - where for other browsers a iframe is not required). If they are using another older browser which is not IE then it can just use location.getHash() in the check (without an iframe as explained before). Both types of checks are designed to be extremely fast and as minimal as possible, bringing the necessary overhead down to next to nothing. It's all about what the browser is actually willing to let you do, and trying to do it using the least intensive code possible.

    Note: Before the v1.4.2-final (August 12, 2010) release of jQuery History the only recognised browsers which supported onhashchange natively was IE8 and above. This has been resolved in all newer versions of the jQuery History project.

    0 讨论(0)
提交回复
热议问题