Re: [w3c/ServiceWorker] Add an option to include frozen documents. (#1442)

For the record I just want to state I find the pushback on `Client.frozen` attribute a bit frustrating.

I acknowledge that using it has a small race condition, but the service worker group specifically accepted that design when it chose to make Client object a snapshot years ago.  I believe this was a tradeoff to avoid the expensive operations required for live updated attributes, etc.  I hope we don't have to re-litigate the Client object design every time we want to add a boolean flag to Client.

Also, freeze state is not changed frequently.  The probability of the race in checking `Client.frozen` actually manifesting is quite small.  Meanwhile, in the majority of cases the attribute could provide real benefit.

Finally, adding `Client.frozen` does not preclude other possible changes to postMessage or other new APIs.  If the race condition issue actually manifests as a problem in practice we still have options.

Given two browser engines are in favor I would hope we could proceed with `Client.frozen`.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/ServiceWorker/pull/1442#issuecomment-532052118