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 was turned on by default in Edge included in Windows 10 Insider Preview Build 17063.
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.
Nagaraju Epuri commented
Any update here?? This is next big thing after XHR. I strongly believe this is going to be a game changer for future web.
Matthias Götzke commented
We are leveraging this in an application used by on site 'technicians'. Usually they have 3 or 4g connectivity, but inside buildings they can become temporarily offline. Which is where service worker kicks in. This is the reason we use android devices not windows phones.