|
|
|
|
|
by mcheely
4471 days ago
|
|
Disabling the cache by default can be troublesome. I'd say it breaks the principle of least surprise - I wasn't aware of this behavior in Chrome, and it's a good thing I develop with Firefox, as I just resolved a bug that only manifested itself when bypassing the browser cache. If the browser cache had been linked to dev tools being open in my case, I probably would have ended up down some false causality rathole around dev tools. |
|
We do plan on making the disable cache toggle more visible (probably with the other buttons at the top of the main panel) and making it very obvious that the cache is disabled.
When we have done that it would make sense to have the button remember state.