Peter Beverloo

We ran two Origin Trials for this API, during which we saw very little use and received no feedback on its functionality. That unfortunately doesn't give us the confidence required...

Using [Web Push Notifications](https://developers.google.com/web/fundamentals/push-notifications) continues to be the recommended option, which will work well in the majority of cases, especially when used with a low `ttl`.

I quite like that idea—we haven't figured out a clear way of listing the events, but I can definitely see this being useful. @mugdhalakhani @engedy FYI

What do you mean by FCM? https://tests.peter.sh/push-message-generator/ can already send messages to FCM, also using the older proprietary mechanism (select that under _authentication_).

The list is updating again, thank you for being patient :) Previous caveats still apply: * Updates will be ran weekly, at 3:35am on Monday morning, Europe/Amsterdam time, * `base::Feature`...

That certainly sounds like an issue on certain builds of Android—this is one of Chrome's manual test cases iirc. The intended behaviour in the spec (& in Chrome's implementation) is...

The [Push Generator](https://tests.peter.sh/push-generator/) has support for delayed requests now. I'll add something to the notification generator soon.

It looks like our implementation issues a warning from Document-contexts, but blocks the request from Worker-contexts. I don't think we currently have metrics in place for measuring how often this...

Without `requireInteraction`, the on-screen display time of a notification will depend on the operating system. The goal here is to make sure users have a consistent, system-wide experience. The `requireInteraction`...

Mind if I tag along to that call, @JaninaSajka, given that I'm involved in both the Push API and Notifications?