Re: Advocacy / prioritization

That would require to define ServiceWorkers as part of an HTTP Header then. Because you can’t execute the JS of the first page if you don’t load the page first (which starts prefetching of urls already via the lookahead).

Can you open an issue regarding this on the repo, I’ll comment on it.




From: Yoav Weiss 
Sent: Monday, September 30, 2013 9:31 AM
To: Brian Kardell 
Cc: Clint Hill ; public-nextweb@w3.org 
Subject: Re: Advocacy / prioritization
I'd add "first load bootstrapping" for ServiceWorker (née: NavigationController), which would enable polyfills to truly control resource loading in the page, starting from the page's first load (unlike the way it is defined today).


As an example, ServiceWorker/NavigationController was mentioned in the past as a way to polyfill CSP. Without it handling the first load, that is not something you can rely on (since first page load users will remain vulnerable). 

Received on Monday, 30 September 2013 12:53:00 UTC