-
SharedWorkers keep living while there'sa web page of the domain that created it open. Since all WebWorkers can create others, and ServiceWorkers live without needing a web page open, I think: if a Ser…
-
We need to define the security policy more concretely. This has lead to a long discussion on the chrome side:
https://codereview.chromium.org/27278002/#msg23
We need to define the restrictions betwe…
alecf updated
9 years ago
-
Which ServiceWorker will they go through? Maybe the scope of a worker should be decided as per iframe. I.e. workers can have a service worker different from the document(s) that created them.
-
Several algorithms use the term atomically. Where is this defined. I'm not sure how atomicity can be enforced, when there are several hooks where JS can run:
1) Promises are returned, which are resolv…
-
I will likely rename client to environment in Fetch as it represents an "environment settings object" (from HTML). I don't think it's exposed as a name anywhere yet, however it could be somewhat confu…
-
These shouldn't be specific to ServiceWorker, and should move into the Fetch spec.
These bits stay the same:
```
partial interface ServiceWorkerGlobalScope : WorkerGlobalScope {
readonly attribute…
-
Hi there,
I've been running the equivalent of the JS call:
``` js
chrome.extension.getViews({type: "popup"});
```
From the Gopherjs Chrome Bindings I'm working on:
``` go
c := chrome.NewChrome(…
-
The ability to enumerate the documents open for an origin for the purpose of postMessage'ing seems like a separable piece. The ability to do that would also b useful in Document context or in a Shared…
-
Via http://lists.w3.org/Archives/Public/public-webscreens/2014Aug/0003.html
The specification does not define when the presenting user agent will be able to access the presentation session across pag…
-
ServiceWorker derives from Worker, which exposes terminate()
Should this be a no-op, or...?