- From: Michael[tm] Smith <notifications@github.com>
- Date: Sat, 08 Apr 2017 19:33:15 -0700
- To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Sunday, 9 April 2017 02:33:49 UTC
I am wondering if there’s an inconsistency in behavior here that we should fix. Specifically, in this PR we’re dropping the following normative requirement: > If _workerType_ is not a valid `WorkerType` value, queue a task to fire an event named `error` at the `link` element, and abort these steps. That’s for the case of the `link` element with an a `workertype` attribute whose value is not a valid `WorkerType` value. But in contrast, in the case of `Link` header with a `workertype` attribute whose value is not a valid `WorkerType` value, the spec still says this: > Let _workerType_ be the "`workertype`" target attribute of the `Link` header, or "`classic`" if no such attribute is present. > If _workerType_ is not a valid `WorkerType` value, abort these steps. So we’re aborting when the `Link` header provides a `workertype` value that’s not valid, but we’re not aborting in when a `link` element provides a `workertype` value that’s not valid. Is that an inconsistency in behavior that we should fix? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/ServiceWorker/pull/1110#issuecomment-292759442
Received on Sunday, 9 April 2017 02:33:49 UTC