Provides web-apps with scripted access to server-sent notifications.
Push API is now in development: https://developer.microsoft.com/en-us/microsoft-edge/platform/status/pushapi
Firebase Cloud Messaging (FCM) blows the W3C/IETF Success Prevention Depts out of the water!
See my comment below 4-Jul-16. Edge engineers no longer have an excuse to hamstring Microsoft Hub Notification broadcasts. (NB: Firebase are also working on implementing background geolocation!!!)
Broadcast Messaging and Topic Based subscription is now available to
your WebApp just like native Apps thanks to FCM.
I am absolutely ecstatic about this, as we all should be, and equally
grateful to FCM for having managed to bypass the recalcitrance and sheer
bloody-mindedness of spec-authors to provide functionality that everyone
outside the ivory-towers was begging for.
Anyway rejoice and be glad as Native Apps have one less stick to beat us
over the head with. And you Firefox fans are no longer stuck with
Mozilla's third-rate AutoPush!
Now if we can only get background geolocation with ServiceWorkers
nothing can stop WebApps: -
Still under development??
Алексей Мичник commented
Glad to see at least something useful whis is not "under consideration"! Great! Hope development will be completed soon
[[[ I've sent the following to Elio Damaggio of Microsoft ]]]
Can you please help me with a conundrum I simply cannot work out by myself?
How can the author of this comprehensive problem description and technically brilliant solution: -
be the same person to allow his name to be put to this second rate piece of ****: -
Why can't Web Apps subscribe to Topics with all device-topic matching done in the Push Service totally unseen from the Application Server?
Why do you hate us?
Cheers Richard Maher
Regardless of W3C and IETF handicapping, please support Windows Notification Hub topic-base multi-cast to the UI: -
Topic-based multicast. Broadcasting push notifications to different markets, based on interests of individual users, requires efficient pub sub routing and topic-based multicast logic
I would be grateful if Microsoft would take an active roll in specification formulation
Vivek Khandelwal commented
Looking forward to this !!
Thank-you for prioritizing this and Service Workers!
PS. Please update your compatibility/support icons. The Push AP is NOW supported by Chrome, FireFox, Opera, and Safari, and the Android browser.
Nikola Nikolic commented
This is related to service workers
I just assumed this was supported in 1.0... guess not. Maybe they're holding off until they figure out some way to shoehorn Cortana into this functionality.
Mohamed Hafez commented
Really important new feature, please add! Edge/IE is now the only major browser not supporting some kind of an offline Push API, would be a great start for Edge to show Microsoft will now keep up with new standards.
Phyo Arkar commented
Push api , along with Server Sent Events are a must for RealTime Web. It makes things a lot more simple vs Websocket.
Nikola Nikolic commented
This is a MUST for modern browser!
scott schmitz commented
would like to see
Simeon Vincent commented
Dan, there's some discussion of the differences between the APIs here: https://github.com/w3c/push-api/issues/104#issuecomment-69745798
Simply put, Push API fills a different role than SSE. In addition to Vivian's comment, it seems the push API builds on Service Workers and takes advantage of the OS's native push support. When the browser receives a push notification, it will spin up a service worker that will handle the message. Some additional discussion can be found on Google's Intent to Ship announcement for Push API .
Dan, the browser does not need to be active.