Issue metadata
Sign in to add a comment
|
Modified scripts and CSS not reloaded on F5 when working on localhost.
Reported by
noelabra...@gmail.com,
Nov 3 2016
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.87 Safari/537.36 Steps to reproduce the problem: Previously my workflow when developing a website on my workstation has been to make changes to the .js or .css files then refresh Chrome using either F5, the reload icon, or right-click "Reload". This used to work fine; I'd always immediately see any changes I had made to the .js or .css files (reflected in the rendered page). As of a few days ago, the refresh no longer works or only works intermittently. I now have to hit Control + F5 (or have Dev Tools open with the "Disable cache (while DevTools is open)" checked). This may sound like a small inconvenience, but considering the frequency of my F5 usage (God knows: 5000 times a day?!) it is quite a nuisance. Does anyone know why the behaviour has changed in Chrome? I am on version 54.0.2840.87 m. I should also add that I'm working on a singe-page-application and currently load about 500 .js, .css and .json files on the page during development. Have I hit some kind of limit after which Chrome no longer automatically reloads on F5 (when working on localhost)? What is the expected behavior? F5 or clicking on the reload icon should reload all stale scripts and stylesheets. What went wrong? The stale scripts and stylesheets are only reloaded when hitting Control + F5. Did this work before? Yes Not sure. Chrome version: 54.0.2840.87 Channel: stable OS Version: 10.0 Flash Version: Shockwave Flash 23.0 r0 Probably related to https://bugs.chromium.org/p/chromium/issues/detail?id=654378 But I am specifically talking about loading resources from a server running on localhost. IMO for this case "Reload" should reload all modified resources.
,
Nov 4 2016
So AFAIU, the "disable cache" checkbox would solve your issues. Why you don't want to enable it permanently?
,
Nov 4 2016
#2 >So AFAIU, the "disable cache" checkbox would solve your issues. Why you don't want to enable it permanently? And why would anyone enjoy being forced to open an extra panel/window that consumes on-screen space just for the sake of compensating the regression? The term "regression" is used in the context of this particular task, of course. For typical users it's an enhancement. Personally, I would use a hotkey utility to map Ctrl-F5 to F5 in Chrome or maybe try setting up a proxy (e.g. Fiddler) that can force no-cache headers either on all urls or just the ones I need so that only one Ctrl-F5 would be required in the beginning, hopefully.
,
Nov 5 2016
Oh wait, you mean you don't have devtools opened? I didn't get it, sorry. In this case, I merge this to the relevant bug you've mentioned.
,
Nov 6 2016
@lushnikov@chromium.org, the issue this has been merged into is marked as "WontFix". Can you please explain what benefit there is not to reload all resources on F5 when developing on localhost? Can't Chrome detect localhost and do this automatically?
,
Nov 7 2016
@Lushnikov, Reading the merged issue further, it says there: > That means Chrome will uses cached contents only when the cached contents are > allowed to be reused, e.g. not expired > My issue looks separate from the merged issue. I'm having trouble with Chrome serving up cached content when the underlying files have been **modified** on localhost. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by eostroukhov@chromium.org
, Nov 3 2016Status: Assigned (was: Unconfirmed)