28504 2015-04-17 10:44:57 +0000 Should SharedWorker have only Exposed=(Window) ? 2017-07-21 10:15:37 +0000 1 1 1 Unclassified WHATWG HTML unspecified PC All RESOLVED WONTFIX P2 normal Unsorted 1 bugs ian annevk bent.mozilla ian jaffathecake jrburke mike Ms2ger ojan travil zcorpan contributor oldest_to_newest 119627 0 bugs 2015-04-17 10:44:57 +0000 Seems like engines don't support SharedWorkers in Workers, so perhaps the spec should be updated to match the reality? Or are there plans to support SharedWorkers in Workers? 119647 1 travil 2015-04-17 23:56:32 +0000 Is there a technical reason engines haven't done this? I didn't think all engines had implemented Workers in Workers either... 119679 2 zcorpan 2015-04-20 11:33:05 +0000 FWIW Presto has supported arbitrary nesting of workers and shared workers since we introduced workers. 119702 3 ian 2015-04-20 21:02:15 +0000 SharedWorkers in Workers are pretty critical for the long-term usefulness of workers, IMHO... 120834 4 jaffathecake 2015-06-09 09:43:45 +0000 SharedWorkers in ServiceWorkers is a feature request from https://github.com/slightlyoff/ServiceWorker/issues/678 too. Additionally, we've had feature requests for being able to generate notification icons within a serviceworker. This requires workercanvas of course, but any pixel work should be farmed off to a worker so it doesn't block fetch (and other) events. Could SharedWorker be tied to the life of the parent context, rather than specifically documents? (https://html.spec.whatwg.org/multipage/workers.html#dom-sharedworker) This would allow a sharedworker to be tied to the lifecycle of a serviceworker and/or documents. 128735 5 annevk 2017-07-21 10:15:37 +0000 Per comment 3. Jake's request is tracked by https://github.com/whatwg/html/issues/411.