Jquery 历史/后退按钮插件的当前状态?
大约一年前，我花了很长时间研究这个问题，我试过了:
I spent a long time looking into this about a year ago, I tried:
- Jquery BBQ 插件
- Jquery 历史插件
- jquery .address 插件
我发现 jquery.address 插件是最好的，但这些东西变化很快.
I found the jquery.address plugin to be the best, but these things change quickly.
最近有没有人彻底研究过这个选项?在我再次集成 jquery.address 之前渴望听到一些想法(我之前没有任何问题)
Has anyone thoroughly researched the options for this RECENTLY? Keen to hear some thoughts before I integrate jquery.address again (I didn't have any issues with it before)
推荐答案
我是History的作者.正如 SnippetSpace 在他的回答中所说，js 与 HTML5 History API 为旧版浏览器提供可选的哈希回退.HTML5 History API 允许您直接修改 url，因此不再需要哈希！耶！
I am the author of History.js which as SnippetSpace has said in his answer works with the HTML5 History API with an optional hash-fallback for older browsers. The HTML5 History API allows you to modify the url directly, so no need for hashes anymore! Yay!
有关后退/前进插件当前情况的列表，您可以在此处查看:https://github.com/Modernizr/Modernizr/wiki/HTML5-跨浏览器-Polyfills
For a listing of the current situation of back/forward plugins you can check here: https://github.com/Modernizr/Modernizr/wiki/HTML5-Cross-browser-Polyfills
由于 HTML5 History API 是一个正确的解决方案对于 back/forward/hash/hashbang 问题，与旧的 hashchange 解决方案相比，这确实是要走的路.哈希的问题包括:访问哈希 url 时双重加载、不同的 url、与禁用 js 的用户共享哈希链接不起作用.
As the HTML5 History API is a proper solution to the back/forward/hash/hashbang problem, it's really the way to go compared to the old hashchange solutions. Problems with hashes include: double load when accessing a hashed url, different urls, sharing hashed links with js-disabled users don't work.
还有一个支持 HTML5 History API 的插件是 jQuery Address，但是它不支持诸如 replaceState 之类的东西，而且我不确定它对 HTML5 History API 的实际跨浏览器支持.但是看看它的 问题列表 我是说它的支持不是好吧.
There is one other plugin which supports the HTML5 History API which is jQuery Address, however it does not support things like replaceState and I'm unsure of it's actual cross-browser support for the HTML5 History API. But looking at it's list of issues I'm saying that it's support isn't that well.
相关文章