lerni

@Mo @phyzical setting browser.cache.disk.enable to false (see above) prevents the issue without having to deactivate cache in dev-console but it also prevents real-live-issues to reveal or with other words – I don’t expect clients & visitor having set that to false.

Mo

Every time I have looked it up, that is what people seem to recommend

Mo

@lerni Enabling "Disable Cache" under "Network" (in developer tools) is (I think) the recommended way to do this

lerni

browserSync is involved but it looks as it doesn't matter how I trigger the reload - pasting, typing, clicking once cached, it's hard to overcome unless I use tricks I don't want clients/visitor to use.

wmk

well, JS on live should be cachebusted; isn't it by default? For frontend there is a hashpathextension that creates unique links to js files

phyzical

i just feel doing stuff like that ends up "cheating" what a client would end up doing but i get why you would 😄

wmk

Firefox should not use caches with <shift> pressed while hitting the reload button. But TBH I often disable FF's cache on my dev environment