The CredentialManagement API is currently under consideration, with a priority of medium.
Service Workers are now under active development in MS Edge. You can track progress at https://developer.microsoft.com/en-us/microsoft-edge/platform/status/serviceworker
See https://groups.google.com/a/chromium.org/forum/#!topic/chromium-dev/kDq4t93zbpA for more detailed discussion.
IMHO Background Geolocatio a.k.a TravelManager would sit nicely here: -
Please consider surfacing the GeoLocation API in the Service Workers Navigator object! It doesn't look like Edge is interested in the GeoFence API (and why should it be).
For background please see: -
Edge looks to be a real watershed in Microsift browsing. Keep up the good work!
Good to see this and the Push API get up! Well done.
This is where it hooks in: -
Push API is now in development: https://developer.microsoft.com/en-us/microsoft-edge/platform/status/pushapi
[[[ 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
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.
The Jury is in, the standard is stabilized, and Microsoft is the only one dragging its feet.
Web Speech is on the backlog with a priority of Medium. You can track status changes at https://dev.windows.com/en-us/microsoft-edge/platform/status/webspeechapiinput
We are currently investigating Web Speech along with script-based accessibility as part of our longer term accessibility investments. This joins our wider ranging accessibility investments detailed in our Microsoft Edge for Developers blog post: https://blogs.windows.com/msedgedev/2016/02/03/2016-platform-priorities/