I thought I sent this email correctly but this isn't listed in the archive
<https://lists.webkit.org/pipermail/webkit-dev/>. Let me send this again.

---------- Forwarded message ---------
From: Asami Doi <asami...@chromium.org>
Date: Thu, Apr 1, 2021 at 8:03 PM
Subject: [webkit-dev] Request for position: Dedicated workers as service
worker clients
To: <webkit-dev@lists.webkit.org>

Hello webkit-dev,

This is a request for position on Dedicated workers as service worker
clients.

*Specification:*
https://w3c.github.io/ServiceWorker/#control-and-use-worker-client
> When the fetch is routed through HTTP fetch, the worker client's active
service worker is set to the result of the service worker registration
matching.

For service worker registration matching:
https://w3c.github.io/ServiceWorker/#scope-match-algorithm
<https://w3c.github.io/ServiceWorker/#scope-match-algorithm>

*Summary:*
This change will affect the 2 parts in the behavior of dedicated workers.

Previous behaviors: 1) dedicated workers were not exposed to service
workers via the Clients API. 2) dedicated workers were treated as part of
their owner document and controlled by the document's service worker
regardless of the dedicated worker script URL

New behaviors by this change: 1) dedicated workers will be real service
worker clients and they will be exposed via the Clients API.
`Clients.matchAll({‘type’: ‘worker’})` will include dedicated workers. The
‘type’ option is an opt-in option and `Clients.matchAll()` returns only
window clients by default. 2) dedicated workers will be controlled by their
own service worker matched with the dedicated worker script URL.

New behaviors are aligned with the spec.


*Chromestatus:*https://chromestatus.com/feature/6591543769038848

*Chromium bug:*
https://bugs.chromium.org/p/chromium/issues/detail?id=906991

Thank you,
Asami
_______________________________________________
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

Reply via email to