[w3c/ServiceWorker] consider Client behavior for windows where initial about:blank is replaced with a loaded document (#1091)

Our current plan is to expose the environment creation URL as `Client.url` when the environment is marked execution ready.  This is a bit confusing for the case where the environment has multiple documents; like when an initial about:blank is replaced with a loaded document.  See:

https://github.com/whatwg/html/issues/2456

My read of the spec and my initial implementation so far expose the about:blank URL briefly as `Client.url`.  In addition, the environment is marked execution ready twice.  Once as about:blank and once as the final loaded URL.  The second time its marked execution ready this basically amounts to updating the creation URL.

Is this intended behavior for the clients API?  I suspect perhaps the intent was not to mark the Client as non-reserved until after the final loaded document is execution ready.

-- 
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/1091