Re: [w3c/ServiceWorker] ready promise is kind of weird with overlapping scopes (#1278)

Ah, I see what you mean. Chrome does (1). Once we start the "ready" process, any subsequent access just gets added as a result callback to the process. After the ready result is known, any access gets back that result immediately.

It does look like the spec needs a kind of "ready promise is being processed" flag to describe that.

-- 
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/1278#issuecomment-364952366

Received on Monday, 12 February 2018 15:15:46 UTC