- From: Kagami Sascha Rosylight <notifications@github.com>
- Date: Tue, 09 Sep 2025 00:56:01 -0700
- To: w3c/push-api <push-api@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/push-api/pull/393/review/3199898026@github.com>
@saschanaz commented on this pull request. > </li> - <li>When the request has been completed, [=queue a global task=] on the [=networking - task source=] using |global| to [=resolve=] |promise| with |subscription| and terminate - these steps. + <li>If |permission| is {{PermissionState/"denied"}}, [=queue a global task=] on the + [=user interaction task source=] using |global| to [=reject=] |promise| with a + {{"NotAllowedError"}} {{DOMException}} and terminate these steps. + </li> + <li>If |subscription| is non-null: + <ol> + <li>If there is an error with |subscription|, then [=queue a global task=] on the > obtain the subscription of a subscription object of a subscription? The process can fail in case the local PushDB somehow is broken and thus relevant data e.g. the endpoint URL and public key can't be accessed (in case of Firefox), but push messages are from push server and thus never stored in a DB. From #408's title one cannot easily link the issue and the DB breakage, as that's nothing to do with push messages - it can break without any message. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/push-api/pull/393#discussion_r2332371486 You are receiving this because you are subscribed to this thread. Message ID: <w3c/push-api/pull/393/review/3199898026@github.com>
Received on Tuesday, 9 September 2025 07:56:05 UTC