New issue
Advanced search Search tips

Issue 666784 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Nov 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Feature



Sign in to add a comment

Disable Cache (Chrome Option)

Reported by catalinb...@gmail.com, Nov 18 2016

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.71 Safari/537.36

Steps to reproduce the problem:

What is the expected behavior?
Developers should be able to Disable Cache altogether on Chrome, while developing. Relying on the Inspector to be open to keep Cache Disabled isn't always an option, plus it is not an option for mobiles.

What went wrong?
At work, we have devices designated for development only, we need Cache Disabled 99% of the time while testing for updates, we'd definitely tweak an option to Disable Cache altogether, if we could.

Did this work before? No 

Chrome version: 54.0.2840.71  Channel: n/a
OS Version: OS X 10.11.6
Flash Version: Shockwave Flash 23.0 r0

Can't think of any reason why this would not be an option in Chrome (independent from DevTools), or maybe it has not been needed so much until now, when mobile development has increased and Cache is only useful for end-users most of the time.
 
Cc: dgozman@chromium.org
Components: -Blink Internals>Network>Cache Platform>DevTools>Network
Labels: -Type-Bug Type-Feature
Moving to devtools & networking. Not sure if this is a networking feature request or a devtools feature request.
We probably won't add an option here. We try to constrain tools for developers to the devtools panel. You could imagine e.g. a lot of duplicate UI for people that also want to simulate different networks without the devtools panel open, or any other setting that devtools provides.

If you are truly desperate, you could serve your resource with cache-control: no-store headers when developing.
Status: WontFix (was: Unconfirmed)
Note that it's possible to open DevTools for mobile browser: https://developers.google.com/web/tools/chrome-devtools/remote-debugging/

For automation I'd propose to use an extension disabling cache over chrome.debugger api: https://developer.chrome.com/extensions/debugger

You can also look into ChromeDriver project for powerful and convenient automation support:
https://sites.google.com/a/chromium.org/chromedriver/

As csharrison@ mentioned, cache-control is always an option as well.

Sign in to add a comment