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)
how to enable? too hard to find.
edge is garbage
Jani Mäkinen commented
Awesome! Great job guys!
Finally! Thank you!
Misha White commented
Another trojan horse specification by w3c/google...
I hope you know how to secure it :D
Great news! Now if you used ServiceWorkers to deliver Background Geolocation the world will be using Edge.
Fausto Oliveira commented
we need this please.
Please be advised that, as promised/threatened, I have added the Trip Summary page and you can now map and replay your trip on Google Maps.
The new version of the code is at the same link https://drive.google.com/open?id=0B7Rmd3Rn8_hDNW1zSWRoXzBTclU
Can someone please try it on Edge 16?
Most important design/proposed-specification change is that TravelManager subscription should now be Client specific. The TravelEvent must contain the intended Client.id (TravelEvent.source.id). This means that the UA must monitor and filter GeoLocation updates per client. I have also added new demo functionality such as a Trip Summary that is displayed when you press the "Arrive" button. The trip can also be replayed onto Google Maps by pressing "Map Trip" or "Replay". If the last and next geolocation updates for the trip are both visible in the Map window then smooth Marker movement is achieved via CSS transitions.
*PLEASE* help Background GeoLocation get up and help Web Apps compete with Native Apps!
If there is something wrong with my TravelManager solution design then let me know. Tear holes in it!
Jani Mäkinen commented
This is a crucial part of the modern web, bring Edge to the same level with this please :) Great work on the browser so far!
I'm sorry Google is so far ahead of you
As promised/threatened. The TravelManager.PollyFill.js file is all Edge developers need to implement in order to be the first browser out there with supportable background geolocation. See aaa_readme.txt here: - https://drive.google.com/drive/folders/0B7Rmd3Rn8_hDNW1zSWRoXzBTclU
Sorry to nag, But it has taken a while now. I know it's a lot to implement but I think that you should start by partially supporting service worker now so we can start using it and not having to wait for every feature to come along. Otherwise it feels like we are going to have to wait another year. Some things we can polyfill ourself. Make a Minimum Viable Product (MVP)
I got a question is there some issue tracker i can follow? (like bugzilla or chromium bugs)
The "Working on it" label is not so appealing
To be fair to Edge Developers, this is a large effort requiring much coordination. (Especially, If Microsoft are to deliver Background Geolocation and Topic Push Message Subscription in Version 1)
May I suggest that you also give Safari Devs at hurry up: -
Filip Chalupa commented
Please is there any status update? How far are we from seeing service workers in at least the insider program? Last message is year old now.
@Jake Archibald *Please* stop blackballing Background Geolocation. Just try operating in a meritocracy for a change where the best ideas are approved by the best available minds. I know it was impertinent and insubordinate to attempt to bypass the W3C/IETF tentacles and go straight to engineering but please don't punish others for my folly!
WebApps *need* Background Geolocation if we are to compete at all with Native Apps. Uber, Dominos, Deliveroo, GrindR, Facebook, Maps and on and ON.
Stop this "Not invented here" nonsense and get on with it!
Service Workers are the conduit; just make it happen!
Are there no adults here?
Jake Archibald commented
"background-fetch monopolized proceedings" - lol it wasn't discussed at all.
David Storey [MSFT] commented
@Richard Maher this is not the venue for debating what was discussed in working group face to face or issues with the spec. Please remain on topic.
Thank you for providing a link to background geolocation suggestion. People that support this will vote accordingly. We will take these votes into account when planning what features to work on in the future.
And, finally, (Sorry for multiple replies) is the Service Worker GitHub "issue" that explains everything: -
And here is the link to what is monopolizing the F2F time of the cognescente: -
Here is the link I added yonks ago: -