Re: [w3c/ServiceWorker] Service worker client URL discrepancy (#1515)

yoshisatoyanagisawa left a comment (w3c/ServiceWorker#1515)

FYI but https://issues.chromium.org/issues/41337436 has been fixed, and now Chromium follows the spec.
With this world, you might need to have a mapping of a client ID and current URL (including a hash fragment).  I did not come up with a way with linear logic flow.


I also think `client.currentURL` can be a choice, but I would like to know other attendees opinions.

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

Message ID: <w3c/ServiceWorker/issues/1515/2840599695@github.com>