Re: [w3c/ServiceWorker] Making a concurrent request for navigations (#920)

Maybe I was unclear. By nullable promise I mean a value that is sometimes null, instead of a promise. That appears to be what your example illustrates.

We should not introduce this new concept that is unused anywhere else on the platform. Everywhere else, if an attribute represents an asynchronous value, it's always accessed asynchronously---it's not sync-if-null, async-otherwise.

-- 
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/920#issuecomment-255884077