- From: Kagami Sascha Rosylight <notifications@github.com>
- Date: Tue, 13 Feb 2024 06:36:20 -0800
- To: w3c/push-api <push-api@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 13 February 2024 14:37:07 UTC
>The concept of “persistent notification” needs to change from “a notification with an associated service worker registration” to a notification with an associated service worker registration or associated push subscription”. Or some other language that clarifies automatically created Notifications from a notification push payload also qualify as “persistent” Can this be "a notification with default action URL"? Such notification would have an action to do regardless of SW or push subscription, and thus can exist in system notification center even after the browser exists (meaning, "persistent"), right? -- Reply to this email directly or view it on GitHub: https://github.com/w3c/push-api/issues/360#issuecomment-1941652310 You are receiving this because you are subscribed to this thread. Message ID: <w3c/push-api/issues/360/1941652310@github.com>
Received on Tuesday, 13 February 2024 14:37:07 UTC