removed extra semi
Update usage of Response objects to more closely match //fetch.spec.whatwg.org/#response-class
Slightly more terse way of writing a JSON response
Keep whitespace consistent with previous formatting
Update Cache.add(...requests), Cache.put(request, response), Cache.delete(request, params) algorithms based on Cache.batch(operations)
Merge pull request #388 from matthew-andrews/response

Update usage of Response objects to more closely match fetch spec
Merge pull request #358 from financeCoding/nit

removed extra semi
Address #385: xrefs to potentially secure origin
Make a note for the condition to pass over the potentially secure origin rule
Update to latest TS and fix the TS build.
Adds self.scriptCache in service worker global scopes. Refs #193
Address #190: change to Client.postMessage(message, transfer)
Removed "on" prefix when describing events

Per issue #214, removed what I believe to be the last instance of "on"
prefixing an event name.
Merge pull request #392 from KenjiBaheux/nit-on-prefix

Removed "on" prefix when describing events
Thanks.
Add the [Exposed] extended attributes
Making document a param of [[Register]] and [[Unregister]]. Fixes #390.
Address #393: change to fire updatefound on a ServiceWorkerRegistration object
Update CacheStorage sections (in progress)
Cause a Content-Security-Policy: sandbox header to unregister the Service Worker at that scriptURL.

Joshua Peek suggested that this should work
(http://lists.w3.org/Archives/Public/public-webappsec/2014Jul/0109.html)
because `sandbox` gives the resource a unique origin, which combines with
Service Workers' same-origin policy to disallow execution.

See slightlyoff/ServiceWorker#113 and slightlyoff/ServiceWorker#224.