- From: Alastair Coote <notifications@github.com>
- Date: Mon, 13 Dec 2021 09:02:21 -0800
- To: w3c/push-api <push-api@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 13 December 2021 17:02:33 UTC
Just bumping this, curious to know if there is any further consensus. I've recently discovered that I can successfully encrypt a Web Push payload via the Web Crypto API but can't send in Chrome because of CORS issues. A quick examination: - Mozilla (`updates.push.services.mozilla.com`): 👍 - Chrome and Opera (`fcm.googleapis.com`): 👎 - Edge (`wns2-by3p.notify.windows.com`) 👎 It would be great to get more consistency here, IMO true P2P sending is an interesting possibility. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/push-api/issues/303#issuecomment-992681061
Received on Monday, 13 December 2021 17:02:33 UTC