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

1. It remains fully encrypted. (This should follow from the PR. We only parse the payload post decryption.) In case of encryption failures you'd have to do some kind of fallback or drop the message on the floor. Essentially whatever happens today for that case.
2. This would remain the same. I suspect that changing this would require larger infrastructure changes and the idea here is for this to be a possible drop-in replacement of opaque messages.
3. Given the answer to 2 I expect no impact here, but I might be missing something.

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

Message ID: <w3c/push-api/issues/360/2474072646@github.com>