This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
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?
Is there a technical reason engines haven't done this? I didn't think all engines had implemented Workers in Workers either...
FWIW Presto has supported arbitrary nesting of workers and shared workers since we introduced workers.
SharedWorkers in Workers are pretty critical for the long-term usefulness of workers, IMHO...
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.
Per comment 3. Jake's request is tracked by https://github.com/whatwg/html/issues/411.