After the update of firefox 23, whenever I click back button doesn't reload the page.
Before the update everything was working fine, but yesterday after the update I noticed that whenever I open a page and after that I hit back button, it doesn't reload the page like before. It's annoying, because I use forum and sometimes is confusing when I open a thread and after that it still says that "new thing", the only way to remove it is to reload the page from the refresh button.
Additional System Details
- Google Update
- Shockwave Flash 11.7 r700
- Adobe PDF Plug-In For Firefox and Netscape 10.1.7
- Next Generation Java Plug-in 1.6.0_33 for Mozilla browsers
- NPRuntime Script Plug-in Library for Java(TM) Deploy
- VLC media player Web Plugin 2.0.2
- The QuickTime Plugin allows you to view a wide variety of multimedia content in Web pages. For more information, visit the QuickTime Web site.
- RealPlayer(tm) LiveConnect-Enabled Plug-In
- Windows Presentation Foundation (WPF) plug-in for Mozilla browsers
- DRM Netscape Network Object
- Npdsplay dll
- DRM Store Netscape Plugin
- Windows Multimedia Services DRM Store Plug-In
- User Agent: Mozilla/5.0 (Windows NT 5.1; rv:23.0) Gecko/20100101 Firefox/23.0
Hi kram160, no solution was found in this thread. I haven't searched for other nytimes threads.
Meanwhile, I think the workaround would be to right-click the Back button and use the list to back-navigate, or use the in-page navigation links to return to the home page or section where you were before. That's all that comes to mind at the moment.
jscher2000: Thanks for the response. So is this a Firefox thing? Are they aware of it?
Hi kram160, as you scroll down on some of these sites, a script in the page pushes new addresses into the browser history. Why isn't it showing up in all browsers?? Are other browsers blocking it and should Firefox block it?? I have more questions than answers.
Unless this is something pages should not be allowed to do, then I don't think anyone will work on changing it in Firefox, and it would be left to add-on developers to find a way to block it.
But that's just an opinion of a support volunteer and for all I know this might be under discussion somewhere.