Re: [w3c/ServiceWorker] should clients.claim() control reserved Clients? (#1090)

> That clarified, clients.claim()'s main role is to cover the case where a client initially called the registration function and the case when a registration with more specific matching scope is registered. Coming back to OP, I'm not so sure, but for the latter case clients.claim() should take control of reserved clients?

So my concern is I'm having a really hard time figuring out how to implement claiming reserved clients.  I can't use scope matching reliably because we don't really have the creation URL yet.  Also, the code calling claim() is probably running in another process, so trying to search all browser processes for in-flight network requests with a match reserved Client is quite hard (and racy).

I would really like to just say claim() does not operate on reserved clients.  In many ways this is similar to what we do today.  Today if a navigation starts just after a claim(), the resulting client may end up controlled by another reservation or uncontrolled if loaded via hard-refresh, etc.

-- 
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/issues/1090#issuecomment-288762083