Shift-reload no longer refreshing linked CSS or JS files... tried disabling extensions, safe mode, full reinstall and no joy. Any thoughts?
Been using Firefox (and before that, Mozilla) for going on 15 years and never had this problem until recently, with FF24. Holding the Shift key and clicking the Reload button (or, pressing CTRL+SHIFT+R) is no longer bypassing the cache, and I'm forced to go to Options > Advanced to clear the cache in order to re-download linked CSS and JS files. Obviously this is significantly delaying
Steps I've taken trying to find a solution: - Disabled all extensions - Tried Safe mode - Tried Reset Firefox - Tried full uninstall (including deleting the Mozilla directory in /AppData/Roaming) and reinstalling from a fresh download
This is on Windows 7 Professional running Firefox 24.
Toutes les réponses (3)
I haven't noticed a change, but I might not have been paying as close attention as you are.
If you open Firefox's web console (Ctrl+Shift+k) and click off CSS (to remove clutter), click Clear, then reload normally (Ctrl+r), you typically see a lot of 304 Not Modified responses. If you reload using Ctrl+Shift+r to bypass cache, you should see 200 OK responses for those same files instead of 304s. Are you getting that or is your Firefox basically ignoring the Shift key?
Wow, your answer was very helpful, thanks!
Here's what I found:
1. Using the web console per your recommendation, I discovered that I'd inadvertently left out the character encoding declaration at the top of the page. I was notified of this via the following error message:
"The character encoding declaration of the HTML document was not found when prescanning the first 1024 bytes of the file. When viewed in a differently-configured browser, this page will reload automatically. The encoding declaration needs to be moved to be within the first 1024 bytes of the file."
2. Upon adding the character encoding element, the normal shift-reload behavior resume functioning properly again (regardless of whether I triggered it via Shift+Reload button or CTRL+Shift+R).
3. Interestingly, I discovered that *not* having the character encoding element caused the reload behavior to reverse. Meaning: holding Shift+Reload (or CTRL+Shift+R) caused the browser to load from cache, whereas doing a "normal" reload (clicking Reload button or CTRL+R) caused the browser to bypass the cache... precisely the reverse of normal behavior, and the source of my utter confusion on the issue.
Not sure if this qualifies as a bug, but to be sure - I'll be certain to include character encoding from here out!!
Definitely a nonintuitive behavior but I'm glad you found a solution.