Re: [w3c/ServiceWorker] Order of messages to clients in same unit of related browsing contexts unclear (#1355)

In terms of what it would take to make this work in the spec, I think we would need to specify that the client message queue task sources for a unit of related browsing context are all mapped onto the same task queue.  This is necessary because the event loop is allowed to pick and choose between task queues arbitrarily and we don't currently constraint the source-to-queue mapping.

In more detail: From https://html.spec.whatwg.org/multipage/webappapis.html#definitions-3 it's already specified that the clients share the same event loop (per "There must be at least one browsing context event loop per user agent, and at most one per unit of related similar-origin browsing contexts.").  And "All the tasks from one particular task source and destined to a particular event loop...must always be added to the same task queue..." constraints the source-to-queue mapping.  But that's where we run out of spec.

-- 
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/1355#issuecomment-422027854