summaryrefslogtreecommitdiffstats
path: root/chromium/docs/website/site/blink/serviceworker/index.md
blob: 695f40a84ddd6a4deb696461c17761c003be2ef8 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
---
breadcrumbs:
- - /blink
  - Blink (Rendering Engine)
page_name: serviceworker
title: Service workers
---

<div class="two-column-container">
<div class="column">

## For Web Developers

## What is service worker?

See the [service
worker](https://developer.mozilla.org/en-US/docs/Web/API/Service_Worker_API)
documentation at Mozilla Developer Network.

### Debugging

Working with a service worker is a little different than normal debugging. Check
out [Service Worker Debugging](/blink/serviceworker/service-worker-faq) for
details.

## Track Status

Service workers shipped in Chrome 40 (which was promoted to stable channel in
January 2015).

[Is Service Worker
Ready?](https://jakearchibald.github.io/isserviceworkerready/) tracks the
implementation status of service worker at a fine-grained, feature-by-feature
level in many popular browsers.

### File Bugs

Go to <http://crbug.com/new> and include "service worker" in the summary. You
should get a response from an engineer in about one week.

If the browser **crashed** while you were doing Service Worker development, go
to chrome://crashes and cut and paste the Crash ID into the bug report. This
kind of bug report is very valuable to us. (If you do not see crashes in
chrome://crashes it may be because you chose not to send usage statistics and
crash reports to Google. You can change this option in chrome://settings .)

To give feedback about service worker that is not specific to Chromium, use
W3C's [public-webapps mailing
list](http://lists.w3.org/Archives/Public/public-webapps/). Use [the spec issue
tracker](https://github.com/slightlyoff/ServiceWorker) to file bugs against the
service worker spec.

### Discuss

For detailed questions about usage: ask us on
[StackOverflow](http://stackoverflow.com) with the
"[service-worker](http://stackoverflow.com/questions/tagged/service-worker)"
tag.

For important announcements and technical discussion about Service Worker, [join
us at
service-worker-discuss@chromium.org](https://groups.google.com/a/chromium.org/forum/#!forum/service-worker-discuss).

</div>
<div class="column">

## For Chromium & Blink Contributors

...interested web developers are welcome to poke around too!

### Links

*   Spec [issues](https://github.com/slightlyoff/ServiceWorker),
            [FPWD](http://www.w3.org/TR/2014/WD-service-workers-20140508/),
            [ED](https://slightlyoff.github.io/ServiceWorker/spec/service_worker/)
*   [Testing](/blink/serviceworker/testing)
*   Implementation bugs use the
            [Blink&gt;ServiceWorker](https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EServiceWorker)
            component. If you sign-in, you can subscribe to get e-mail updates
            at Profile &gt; Saved Queries.
*   Mailing lists: we use
            [blink-dev@chromium.org](https://groups.google.com/a/chromium.org/forum/#!forum/blink-dev)
            for public discussion.
*   Code reviews: subscribe to the
            [serviceworker-reviews@chromium.org](https://groups.google.com/a/chromium.org/forum/#!forum/serviceworker-reviews)
            group to get a copy of all code review requests.
*   Docs:
    *   [Hitchhiker's guide to Service Worker
                classes](https://docs.google.com/a/chromium.org/document/d/1DoueYsm-UOvqDyqIPd9aGAWWQ1XZKX89CsJXDF7j_2Q/edit)
    *   [How to Implement a Web Platform Feature on Service
                Workers](https://docs.google.com/document/d/1cBZay5IbPHFLtDpFPu7q9XevtydiuTKbqXKIFaBZDJQ/edit?usp=sharing)

</div>
</div>