[w3c/ServiceWorker] useCache attribute design seems very very wrong (#1069)

> If useCache is not a valid boolean value, queue a task to fire an event named error at the link element, and abort these steps.

This is *not* how HTML boolean attributes work. You should never do `usecache="true"` or `usecache="false"`.

Instead this step and the previous should just check for the presence of the usecache attribute. There is no such thing as an invalid value. The attribute is either present or absent; it's value does not matter. That's how boolean attributes work.

This is especially important since the `useCache` IDL attribute is supposed to reflect the content attribute. That will work very very poorly with the above processing model.

-- 
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/issues/1069

Received on Monday, 13 February 2017 06:40:23 UTC