On Fri, Apr 29, 2016 at 6:57 PM, Pontus Östlund <pon...@roxen.com> wrote: > > 28 apr. 2016 kl. 16:56 skrev Chris Angelico <ros...@gmail.com>: > > On Fri, Apr 29, 2016 at 12:53 AM, Pontus Östlund <pon...@roxen.com> wrote: > > The reason is probably that the navigation is cached (per page) in a > ”sessionStorage” once it’s been generated. Now, the sessionStorage you would > think would run out of scope once you restart the browser but that isn’t the > case :\ > > > Hmm, interesting. It doesn't require any restart - our emails crossed, > as I discovered that simply closing the tab and opening a new one (NOT > using Ctrl-Shift-T to reopen a tab) drops the cache. > > > By the way: do you browse the doc from you local filesystem or via a web > server? I noticed that the cache worked so-so when the doc was viewed > directly from the file system, so I disabled the cache when doc pages aren’t > fed via a web server.
I use "pike -x httpserver". It sends back 304s if it finds that the files haven't changed; but reloading the page doesn't result in the index.js being re-requested at all (as shown by Chrome's dev tools), due (it seems) to the client-side cache. ChrisA
