Re: [push-api] Multiple consecutive messages (#168)

In Chrome we fire the `onpush` events in parallel, so especially in a world where additional network access is necessary to fetch the _why_ of a push, all of the messages that would be in the queue will already been executing.

Without understanding the impact of having payloads, I'm a bit hesitant for us to deliver incoming messages sequentially. It could significantly increase the time the UA is active, increasing the chance of failed message deliveries because of external conditions (e.g. memory conditions).

In practice, we haven't seen issues with this either. When wouldn't supporting message collapsing on the push service address this problem? https://github.com/webpush-wg/webpush-protocol/issues/9

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/push-api/issues/168#issuecomment-148427082