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/

6,681 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]Jonathan Sampson [MSFT] shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    43 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...
      • 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 RathMatthew 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 DamWouter 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ạmLewis 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.

      • Nagaraju EpuriNagaraju Epuri commented  ·   ·  Flag as inappropriate

        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ötzkeMatthias Götzke commented  ·   ·  Flag as inappropriate

        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.

      • DiegoDiego commented  ·   ·  Flag as inappropriate

        The best thing after XHR.
        A must have for any serius web application developement.

      • AdeelAdeel commented  ·   ·  Flag as inappropriate

        W3C draft (http://www.w3.org/TR/service-workers/) states:

        "This design borrows heavily from developer and vendor experience with Shared Workers .."

        The current status of service worker in on modern.ie is under consideration: http://dev.modern.ie/platform/status/sharedwebworkers.

        While that of shared worker is "Not currently planned".

        Why are you guys stalling Shared Worker and considering ServiceWorker, when Service worker leverage the core functionality of Shared worker?

      • Hiroshi KawadaHiroshi Kawada commented  ·   ·  Flag as inappropriate

        Mobile web should support offline features. In my opinion, Web doesn't need to get native application scope, but mobile users want features that covers mobility use case and mobile application lifetime. Push notification helps better conversion, connectivity of users life and powerful engagement.

      • Ege ÖzcanEge Özcan commented  ·   ·  Flag as inappropriate

        Service Workers are *essential* for making reliable, high-performance offline applications. Unless we have a miracle happening in the connectivity world, enabling high-bandwidth data access for cheap anywhere in the world, lack of Service Workers is a show-stopper for various kind of offline apps. No, HTML appcache doesn't cover most cases.

      Feedback and Knowledge Base