- From: Marco Colli <notifications@github.com>
- Date: Mon, 26 Aug 2024 13:43:54 -0700
- To: w3c/push-api <push-api@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 26 August 2024 20:43:58 UTC
A `fetch` inside the `push` event is unreliable. The push can be triggered even when connection is not available or it is unreliable. Also, the request written like that can be terminated before finishing... There is a reason if the Push API now supports a payload: that was added later because downloading a payload via `fetch` was not reliable. As for the reasons why a notification is successfully sent but not displayed to the end user, there can be many reasons: https://pushpad.xyz/blog/why-some-web-push-notifications-are-not-delivered-to-the-browser -- Reply to this email directly or view it on GitHub: https://github.com/w3c/push-api/issues/386#issuecomment-2311055900 You are receiving this because you are subscribed to this thread. Message ID: <w3c/push-api/issues/386/2311055900@github.com>
Received on Monday, 26 August 2024 20:43:58 UTC