- From: Anne van Kesteren <notifications@github.com>
- Date: Mon, 03 Mar 2025 02:42:23 -0800
- To: w3c/push-api <push-api@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 3 March 2025 10:42:27 UTC
@annevk commented on this pull request. > + |notification|, and |declarativeResult|'s [=declarative push message + parser result/app badge=]. + </p> + </li> + <li> + <p> + If |result| is not failure, then set |notificationShown| to |result|'s + [=push event result/notification shown=] and |appBadgeSet| to |result|'s + [=push event result/app badge set=]. + </p> + </li> + </ol> + </li> + <li> + <p> + If |notificationShown| is false, then run the [=notification show steps=] Hmm. Isn't that just an artifact from how cookies work as well? Should every specification that potentially fetches something later also point out that cookies currently expire after a little over a year? -- Reply to this email directly or view it on GitHub: https://github.com/w3c/push-api/pull/385#discussion_r1977285345 You are receiving this because you are subscribed to this thread. Message ID: <w3c/push-api/pull/385/review/2653745286@github.com>
Received on Monday, 3 March 2025 10:42:27 UTC