Re: [w3c/push-api] Declarative Web Push: mutable field (Issue #391)

> What's the current understanding of this need?

As I understand it this is expected functionality across most push platforms. It's why the `push` event exists.

> This sounds like the expectation here is that clearing site data should exclude push notification.

Yes, we think that there are scenarios that call for that distinction and we think it's ultimately up to the user agent to make these tradeoffs. It might well make sense to remove X MiB of storage now and preserve a X KiB push registration for over a year, in the event that the push message ends up being really important. There's also a distinction here in terms of end user engagement. They explicitly opted into the push message, but did not necessarily consent to large amounts of storage being used.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/push-api/issues/391#issuecomment-2358554538
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/push-api/issues/391/2358554538@github.com>