Hacker News Reader

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.

View on HN

> native web dev

That has to be the strangest combination of terms I've seen this month.

I've seen people refer to bare metal Javascript, which sounds even weirder.

Ever heard of PhoneGap or Electron?

Yes, and neither of them are native, nor are either of them relevant to my comment.

What was your point again?

You can disable cache while dev tools are open in chrome but its not the default.

And, 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.

What 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

Reply on news.ycombinator.com