Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move issericeworkerready data to canisue #3931

Open
awebdeveloper opened this issue Dec 21, 2017 · 4 comments
Open

Move issericeworkerready data to canisue #3931

awebdeveloper opened this issue Dec 21, 2017 · 4 comments

Comments

@awebdeveloper
Copy link
Contributor

@jakearchibald was of the view that we should move isserviceworkerready data to caniuse.com. can u suggest how do we proceed

jakearchibald/isserviceworkerready#91

@Fyrd
Copy link
Owner

Fyrd commented Dec 29, 2017

Looking through https://jakearchibald.github.io/isserviceworkerready/ it seems a lot of features have support that matches what's on https://caniuse.com/#feat=serviceworkers . I'd suggest using numbered notes to point out any areas where support should be partial and what subfeatures are missing.

@awebdeveloper
Copy link
Contributor Author

awebdeveloper commented Jan 2, 2018

Here are what i think is missing

  1. Debugging support
  2. Background Sync
  3. Caches
  4. Post message doc needs to be updated to inform about service worker limitations
  5. Split fetch into fetch-request and fetch-response or update to mention opera limitations

@awebdeveloper
Copy link
Contributor Author

@awebdeveloper
Copy link
Contributor Author

How do you handle sub features ??

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants