jakearchibald / isserviceworkerready

Tracking the status of ServiceWorker in browsers

Is Service Worker Ready Yet?

Tracks the features of service worker supported in browsers. View the site.

Run locally

To install, run the following in the root of your cloned copy of the repo:

npm install

To serve the site on localhost:8000:

npm run serve

To build the site:

npm run build

Contribute

To update data, edit data.json, which is in this format:

  //...

  "features": [

      //...

      {
        "name", "Feature name or <code>interface.whatever</code>",
        "description", "Brief feature details, html <strong>allowed</strong>",
        "chrome": {
          // 1 = supported
          // 0.5 = supported with caveats (eg flags, nightlies, special builds)
          // 0 = not supported
          "supported": 1
          // (optional) browser version
          "minVersion": 35,
          // (optional) alternate icon, currently supports:
          // "chrome-canary"
          // "firefox-nightly"
          // "webkit"
          // "opera-developer"
          "icon": "canary",
          // (optional) details, cavats, links to tickets, flags etc
          "details": [
            "Requires <a href=\"https://www.google.co.uk/intl/en/chrome/browser/canary.html\">Chrome Canary</a>"
          ]
        },
        "firefox": {},
        "opera": {},
        "safari": {},
        // (optional) details that don't apply to a single browser
        "details": [
          "<strong>Chrome & Firefox</strong>: sitting in a tree K-I-S-S-I-N-G"
        ]
      },

      // ...

  ]

isserviceworkerready's Issues

iOS Safary does support offline web apps now

So, I have just found that offline web apps do work in iOS 10 latest Safary.
Try yourself. Here is a simple offline web app: https://ember-doto.herokuapp.com/

Do I miss something or it's time to update that @jakearchibald? https://jakearchibald.github.io/isserviceworkerready/

UPD: I find that other PWAs don't work offline. Only the one referenced above. :\

Add support for the `Service-Worker-Allowed` header

Is phantomjs serviceworkerready?

I'm trying to test using service workers with localforage. They use phantomjs for the unit tests. I run into navigator.serviceWorker.register is undefined in phantomjs. The tests run fine in Chrome en Firefox nightly. I cannot find any documentation on serviceworker support in phantomjs. It is not listed here http://trac.webkit.org/wiki/QtWebKitFeatures22#WebDeveloperFeatures . Does that mean it is not supported?

Add entry about geofencing

This is being discussed: https://www.w3.org/TR/geofencing/

Maybe shall be added to the site?

Edge supports background sync

…since they switched to Chromium apparently.

See https://learn.microsoft.com/en-us/microsoft-edge/progressive-web-apps-chromium/how-to/background-syncs and https://caniuse.com/background-sync

Include UC Browser

Plz include info for uc browser as it's the biggest browser in India, china and this part of the world

Safari Technology Preview 46 enables Service Workers by default

Per https://webkit.org/blog/8042/release-notes-for-safari-technology-preview-46/:

Made Service Workers enabled by default

🎉

Looking at that changelog for Service Workers alone and previous ones, I suspect several features need to become green? 0:-)

Navbar highlighting is broken

When the user hovers over navbar items, the item which is styled is often not the one which is hovered over. It appears as something gets "stuck" and the item which is styled is the one which was first hovered over. I can reproduce this behavior in multiple environments on Chrome and I cannot reproduce it locally on MS Edge.

postMessage to & from worker fails in Chrome 41

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

Error, TypeError: undefined is not a function

Here:

isserviceworkerready/src/demos/postMessage/index.html

Line 38 in f0c3e98

sw.postMessage({

include information on serviceworker push notification usability

It would be nice to include information on serviceworker push notification usability. I don't know how easy it is to actually test this, though.

Indicate Chrome IOS support

Viewing isserviceworkerready, I was given the impression chrome supported this on "mobile".

I could not detect Chrome support in the IOS build - Checked Chrome 46 on IOS 9.1 on 20151121.

IMHO, that is a distinction with barriers (wait till IOS10?) worth tracking, particularly on a "readiness" site. At the very least, this site should clarify that this is an "Android only" feature.
If there is no future track to IOS, it should state that, too.

postMessageing a MessageChannel to a service worker is only partially working

Until http://crbug.com/432678 is fixed, passing a MessageChannel to a service worker for two way communication only works when the service worker and client happen to be running in the same process.

Add entry for WindowClient.navigate

https://www.chromestatus.com/feature/5314750808326144

Plus, Mozilla intents to ship in Firefox 51: https://groups.google.com/forum/#!topic/mozilla.dev.platform/azNSLhfv978.

Add self.serviceWorker

Arose from w3c/ServiceWorker#1077

Added to spec in w3c/ServiceWorker#1426

Tracking Push API

Hi!
I think there's lack of valid information about browsers' support of Push and Notification API. They're not part of SW spec, but so does BackgroundSync, and a lot of people intents to use service worker for notifications. There are still details like lack of support of push payload, which is present in Android Push, which people find confusing.
What do you think about including such info in this repo?

iOS 12.2 safari does not support service worker

Samsung Browser

As you're explicitly calling out (Chromium-based) Opera, can you also explicitly add (Chromium-based) Samsung Browser to your list? Samsung browser has pretty significant market share among mobile browsers, see http://gs.statcounter.com/#mobile_browser-eu-monthly-201504-201604 and is definitely shipping Service Workers, see http://developer.samsung.com/technical-doc/view.do?v=T000000245L.

Chrome mobile and media caching

Chrome mobile <52 is currently bypassing the SW (as far as I know) for media (audio/video) requests. Is there an appropriate place to note this on this page? as may confuse many developers.

More info

Chrome canary now has flag-free service workers

All tests appear to pass...

Include information about privacy and administration

This seems to be the main source of information about ServiceWorker, but there is no information for the user, how is the user informed about service worker usage in different browsers (does the browser ask a question or show an icon), or how does it manage (does the browser gives the user any option to manage or manually unregister service workers).

This kind of info could be useful both to developers and to users, and is absent almost everywhere. The only resource I found about this is: https://www.ghacks.net/2016/03/02/manage-service-workers-in-firefox-and-chrome/ .

Add test for isReload

It seems browsers do not propagate isReload flag correctly. If I reload the page in the browser, only the main resource gets isReload set to true, but all subresources do not. This makes it really hard to know where you have to handle caching in some special way.

Indication of support on mobile platforms

Maybe I missed something, but it'd be nice to show mobile support, e.g. Sure ServiceWorker works in Chrome 35+ on desktop, but does that also carry over to mobile? (obviously not on iOS as it's just a WebView - this should be clear in the UI).

If Chrome on Android and Chrome on desktop have feature parity by version number then this is obviously irrelevant and I'm talking out of my trousers, but I think I'm right in saying this is probably not the case (please correct me...).

Or did I miss something patently obvious?

Edge 17 enables Service Workers by default

Per https://developer.microsoft.com/en-us/microsoft-edge/platform/changelog/desktop/17063/?compareWith=16299:

The Service Workers family of features (Service Worker, Push API, Cache API, Fetch API) is now enabled by default in Microsoft Edge. You can learn more about these features in our post Service Workers: Going beyond the page. Note that Service Workers are not yet enabled by default in Hosted Web Apps.

⇒ https://blogs.windows.com/msedgedev/2017/12/19/service-workers-going-beyond-page/

🎉

Please explain the "simple demo" for sync fully

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

Looks like black magic

Where is the showNotification call?

Please point me to any other documentation on this.

Safari status needs to be updated.