ServiceWorkers (formerly Navigation Controllers) are a new system that provides event-driven scripts that run independent of web pages. They are similar to SharedWorkers except that their lifetime is different and they have access to domain-wide events such as network fetches.
Service Worker and friends are enabled by default in EdgeHTML 17 released today (30/04/2018)
David Storey [MSFT] commented
@Richard Maher I don’t have a narrative. This vote is for the specification listed. There are separate voted for Fetch, Push, and so on. I don't see any APIs listed for background geolocation in the link you provided. Like I mentioned previously, if you want to show developer interest and spot for Background Geolocation then create a feedback item and have people vote for it, like they have for other features on this site. Without that we have no way of knowing if they want that feature.
@David, I am sorry that the facts do not support your (and W3C's and IETF's) narrative of Background-Geolocation being completely divorced from Service-Workers. One merely needs to peruse the Tokyo F2F agenda (link posted in previous) to see just how much time background-fetch monopolized proceedings. To pretend via smoke and mirrors that "Fetch" is an intrinsic part of Service Workers but "Background Geolocation" is not would be to treat the user-base as absolute fools :-(
Apart from that hypocrisy, let me please draw everyone's attention to the current Service Worker specification: - https://www.w3.org/TR/service-workers/#extensibility
David, the fact that you, and others, may not be able to see the obvious plug-n-play correlation between this Service Worker Extensibility and Background GeoLocation is neither here nor there.
Edge users voting for Service Workers ARE voting for background-geolocation, background Fetch and Background Notifications and so on.
The cynical attempt to ring-fence funding and development effort toward the pet-projects of the privileged few is not something I will stand idly by and witness!
David Storey [MSFT] commented
Hi @Richard Maher. This request is for Service Worker. To not dilute the discussion and make it clear what is being voted on, please open a separate feedback item for Background Geolocation. Thanks!
For those hoping that W3C/IETF will wake up to the background geolocation requirement, I'm afraid the answer is "Not this year" :-(
Still, at least the sponsors are getting value for their money and quality F2F time in Tokyo: -
You just can't be that productive via email or a conference call!
Hav no idea what Microsoft representatives (Ali Alabbas, Jatinder Mann) were doing there
Humayun kabir commented
Please help me sir....
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: -
Focus on getting it "right" first, and then add features like offline sync, push etc later...
Thank you guys
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!
Vincent Kammerer commented
Nice to see microsoft doing it! I guess we'll have to wait until 2020 to get it in Safari...
Good to see this and the Push API get up! Well done.
Thanks for prioritizing this for Edge. Does this mean it will also be implemented for the Universal Windows Platform?
Yay Go Microsoft Go!
Matthew Rath commented
This needs to be implemented as soon and as thoroughly as possible.
The single biggest problem i face as a developer of 8 years is how to make websites handle poor or even no connectivity.
Chrome and opera already have their own implementations and FF will be migrating from their nightly build soon enough -
Move your *** MS or get left behind.
For Hosted Web Apps (HWA) aka Westminster service workers will replace the depreciated AppCache and give developers far more granular control over what they cache and when.
If AppCache it to truly be depreciated, support for service workers needs to be added sooner rather than later.
Umberto Arreghini commented
Service worker is a fundamental feature for web apps development.
Wouter van Dam commented
We are looking to install several hundred machines in the upcoming months and expect to be installing another batch in the months after that. Currently an evaluation is going on to decide whether all these machines will be running Android or Windows 10 with Edge. Implementing this feature - preferably including background sync - would strengthen the case for the Windows solution.
Can i haz this now plz, k thks bye
Lewis Phạm commented
@Adeel The major difference between SharedWorker and ServiceWorker is lifetime. ServiceWorker is an event emitter with a temporary lifetime, while SharedWorker remains persistent until all pages are closed.