How can we improve the Microsoft Edge developer experience?

Service Worker

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.

https://github.com/slightlyoff/ServiceWorker/

7,719 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Jonathan Sampson [MSFT] shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    53 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...
      • David Storey [MSFT] commented  ·   ·  Flag as inappropriate

        @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.

      • Richard Maher commented  ·   ·  Flag as inappropriate

        @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  ·   ·  Flag as inappropriate

        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!

      • Richard Maher commented  ·   ·  Flag as inappropriate

        For those hoping that W3C/IETF will wake up to the background geolocation requirement, I'm afraid the answer is "Not this year" :-(
        https://github.com/w3c/ServiceWorker/issues/1053

        Still, at least the sponsors are getting value for their money and quality F2F time in Tokyo: -
        https://twitter.com/jaffathecake/status/848018836922093570

        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

      • Anonymous commented  ·   ·  Flag as inappropriate

        Fantastic news..
        Focus on getting it "right" first, and then add features like offline sync, push etc later...

        Thank you guys

      • Richard Maher commented  ·   ·  Flag as inappropriate

        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: -
        https://github.com/w3c/geofencing-api/issues/25
        https://github.com/slightlyoff/ServiceWorker/issues/745

        Edge looks to be a real watershed in Microsift browsing. Keep up the good work!

      • Anonymous commented  ·   ·  Flag as inappropriate

        Thanks for prioritizing this for Edge. Does this mean it will also be implemented for the Universal Windows Platform?

      • Matthew Rath commented  ·   ·  Flag as inappropriate

        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 -

        https://jakearchibald.github.io/isserviceworkerready/

        Move your *** MS or get left behind.

      • Wouter van Dam commented  ·   ·  Flag as inappropriate

        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.

      • Lewis Phạm commented  ·   ·  Flag as inappropriate

        @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.

      Feedback and Knowledge Base