Chrome与Firefox后退缓存 [英] Chrome Vs Firefox Back Caching
问题描述
我有一个drupal网站，其视图链接到详细信息页面.该视图具有分页.这是问题所在:
I have a drupal site with a view that links to detail pages. The view has paging. Here is the issue:
-
在FireFox中，当您从视图的第8页转到详细信息页面时， 然后点击后退"按钮，您最终会进入视图的第8页. (好)
In FireFox, when you go from page 8 of the view to a detail page, then click the back button, you end up at page 8 of the view. (good)
在Chrome中，当您从视图的第8页转到详细信息页面时， 点击后退按钮，您最终会进入视图的第1页. (不好)
In Chrome, when you go from page 8 of the view to a detail page, then click the back button, you end up at page 1 of the view. (bad)
给我的印象是chrome和firefox以相同的方式处理了反向缓存.这不是真的吗?我有什么办法可以修复它，也就是说，无论哪种情况，您都可以在单击后退"按钮后进入视图的第8页?
I was under the impression that chrome and firefox handled back caching in the same way. Is this not true? Is there anything I can do to fix it, i.e., so that in either case you end up at page 8 of the view after clicking the back button?
您可以在 http://www.instepp.umn.edu/上看到我在说什么.出版物
谢谢！
劳里(Laurie)
推荐答案
Digging around a bit more, I found the same question at: Firefox back button VS IE and Chrome back buttons
博客文章的答案为: http://madhatted.com/2013/6/16/you-do-not-understand-browser-history
简而言之，Chrome浏览器上的后退"按钮Firefox的行为有所不同；如果我期望的行为是使后退按钮从缓存中返回DOM，那么我将无能为力.如果我希望后退按钮返回上一页的刷新版本，则可以使用博客文章中详细介绍的选项.
In short, the back button on Chrome & Firefox behave differently; nothing I can do about it if my desired behavior is for the back button to return the DOM from cache. If I want the back button to return a refreshed version of the prior page, I have options as detailed in the blog post.
这篇关于Chrome与Firefox后退缓存的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
