Forum Discussion
Dev channel update to 96.0.1032.0 is live
MarkBarbieri Can you try a demo: https://gauntface.github.io/simple-push-demo/
If it fails, navigate Edge to edge://push-internals. This is a diagnostic page that captures push messaging errors. Please provide the contents of this page, although you can remove "Endpoint", "Device ID", and "Channel ID". The last section about errors is most important.
josh_bodner The push demo gives me the prompt to allow notifications when I enable them on the page, but fails with a CORS error when I try to Send a Push (see attached)
edge://push-internals output also attached.
Thanks
MarkBarbieri that might be a red herring. I hadn't noticed when I sent it, but that demo site appears to be broken in general (it fails with that same error in every browser...) If you have a site that you normally use that can send you notifications on-demand, could you get the same info when you see a failed notification from it? Otherwise, how about a different demo site like https://webpushdemo.azurewebsites.net/?
josh_bodner OK, that site worked, but still no notification. I tested that site on Windows (Edge Dev release) and I get notifications there, but not on the Mac.
Let me know if the attached is not enough info.
This is another simple one that works on Windows, but not Mac
https://www.bennish.net/web-notifications.html
Interestingly it doesn't add any output to edge://push-internals
MarkBarbieri sorry for the delayed response! It's actually by design that that Bennish site doesn't output anything to push-internals. There are multiple ways to show toast notifications, and Push is just one way of doing that. Bennish doesn't use Push though, so between that and the output from push-internals, it looks like Push is working fine, and the problem is on the toast side.
So, can you try that Bennish site again, and maybe also https://web-push-book.gauntface.com/demos/notification-examples/, and then afterwards, copy over the contents of edge://histograms/Notification (if you open that histogram page before doing the tests, make sure you refresh the histogram page after doing the tests). Also, do you have Chrome on the machine, and can you see if Chrome is having the same problem? Ideally, the same channel of Chrome as Edge?
