Re: [ServiceWorker] Document the headers being introduced (#717)

@jakearchibald The spec should clarify that, then - because it's a non-guaranteed behaviour as implemented in Chrome.

open standard - The SW spec is part of the W3C WebApps WG, right? If so, yes, it's already covered, so  no need for a separate doc. You can see some of the Provisional registrations (e.g. the many CORS headers). The absence of Content-Security-Policy I don't recall whether that was because of some of the IETF vs W3C stuff or just an oversight.

re: `maxScope` - here's what the language currently reads:
> Let maxScope be the result of parsing serviceWorkerAllowed with registration's registering script url.

Here's what it probably should be:
> Let maxScope be the result of resolving serviceWorkerAllowed relative to the registration's registering script url.


---
Reply to this email directly or view it on GitHub:
https://github.com/slightlyoff/ServiceWorker/issues/717#issuecomment-114851853