I have a drupal site with a view that links to detail pages. The view has paging. Here is the issue:
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)
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)
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?
You can see what I'm talking about at http://www.instepp.umn.edu/publications
Thanks!
Laurie
Digging around a bit more, I found the same question at: Firefox back button VS IE and Chrome back buttons
It was answered by the blog post at: http://madhatted.com/2013/6/16/you-do-not-understand-browser-history
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.
Related
I'm not sure why, but it works across every other internet platform.
First Pic is of button in IE, Second is code, third is button in Chrome.
Link to webpage
I can't post a comment because of my low reputation so here we go.
Did you open this page in IE prior to adding this style? In my experience, IE has a very aggressive caching policy and will often not reload css files and such.
We have just encountered a Chrome (65.0.3325.181) and Opera (52.0.2871.37) scrolling bug. This is on an intranet page so I can't give you a URL. But if the following symptoms are familiar to you, and you know the specific cause and a fix, please advise.
The scrollbar appears, and about 9 of 50 items can be scrolled vertically into view, at which point scrolling stops. It's as if the page believes there are no more items to be displayed.
However, if a new tab is opened and the URL from the broken page is pasted into its address bar, so that the page is retrieved from cache, scrolling works perfectly in the new tab.
I have a typical CSS site menu/sub-menu system on a site I built. When viewed in Chrome (latest version, on Windows), each link in each sub-menu requires TWO clicks for the link to work. The first click appears to do nothing at all. It's fine in all other browsers.
I have pared the code down to the minimum that demonstrates the behaviour. You can see the result here: https://www.harmonysite.com/chrome-issue.htm Clicking on the "Sub-menu item" link does nothing in Chrome - the FIRST time. Click it a second time and it works as expected. In other browsers it works the first time.
Any advice would be appreciated.
I have a menu iframe and a body iframe setup. In IE when I click the "back" button in the menu it goes back just fine. In chrome it works fine for the most part but there is one instance of that link that will open it in a new page even though it is a replica of other working instances of that back button.
Any ideas of what would prevent a link from working in chrome, a link that works just fine in firefox and IE?
I have a body iframe and a menu iframe.
the menu has links...some of them are targeted at the menu...the new page will redirect the body on load.
sometimes the menu link just updates the body as it doesn't need a menu.
in IE it works great. Firefox and Chrome do not like it. It will work fine the first time. But when you go back and click the link that JUST worked...it will open up in a new tab instead.
New Info:
I did a bunch of research on the issue and apparently
it's a chrome and ff update that is trying to disable iframes. I have yet to find a solution...if you have one let me know!
Mine is something of a newbie question which I'm hoping someone can shed some light on.
I have a table of contents on my page, with titles which link to sections further down the page.
the targets are created like this;
<a name='appendix'>Appendix</a>
and the links are created like this;
<a href='#appendix'>Jump to Appendix</a>
Now when you tap on the link in iphone safari, it takes you straight there no problem. However if you scroll back to the top, to the ToC, and tap the same link again, the browser does nothing.
Looking at the url I can see #appendix on the end and I assume that tapping the link again, the iphone believes its already at that link, since the url already has #whatever on the end.
Normally I'd be happy to leave it that, but the iPad, Android and Blackberry all behave as I'd expect, ie no matter where you are on the page or whether you'd tapped on the same link previously, they jump to the target section.
One thing I'm thinking about trying is embedding the whole page in a frameset so its url never changes, although being a noob I've no idea whether that'll even work.
Has anyone come across this before? Any ideas?
Thanks
This appears to be an issue with iOS not you. If it has been working on all other devices I am afraid there is nothing you can do except report it to Apple. However, has your iPhone been acting crashy lately, and have you tried it on other iPhones?