4 ms·
I had something like that once in native web dev. It turned out that by default when using the debugging pane the browser would disable cache so the issue (what
by MBCook 8y ago
I had something like that once in native web dev. It turned out that by default when using the debugging pane the browser would disable cache so the issue (whatever it was) disappeared.
Close debugging? It broke again.
Maddening.
- filleduchaos 8y ago> native web dev That has to be the strangest combination of terms I've seen this month.
- skocznymroczny 8y agoI've seen people refer to bare metal Javascript, which sounds even weirder.
- kroltan 8y agoEver heard of PhoneGap or Electron?
- filleduchaos 8y agoYes, and neither of them are native, nor are either of them relevant to my comment. What was your point again?
- efrafa 8y agoYou can disable cache while dev tools are open in chrome but its not the default.
- scrumbledober 8y agoAnd, annoyingly, if you check the disable box any time you close the dev tools it resets to unchecked. If you reopen dev tools it still remains unchecked.
- rising-sky 8y agoWhat version of Chrome did you experience this in? I've never had to re-check the "disable cache" checkbox, even after restarting chrome from a crash state. I am currently at version 67.0.3396.87
- maskedSlacker 8y agoSchrodinger's Bug