- From: Jungkee Song <notifications@github.com>
- Date: Tue, 29 Nov 2016 17:10:51 -0800
- To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
- Message-ID: <w3c/ServiceWorker/pull/1014/review/10674886@github.com>
jungkees commented on this pull request. > - <p>A <a href="#dfn-service-worker">service worker</a> has an associated <dfn id="dfn-foreign-fetch-origins">list of foreign fetch origins</dfn> whose element type is a <a for="/">URL</a>. It is initially empty.</p> + A <dfn export id="dfn-service-worker" for="">service worker</dfn> is a type of <a>web worker</a>. A <a for="/">service worker</a> executes in the registering <a for="/">service worker client</a>'s <a for="/">origin</a>. + + A <a for="/">service worker</a> has an associated <dfn export id="dfn-state">state</dfn>, which is one of *parsed*, *installing*, *installed*, *activating*, *activated*, and *redundant*. It is initially *parsed*. + + A <a for="/">service worker</a> has an associated <dfn export id="dfn-script-url">script url</dfn> (a <a for="/">URL</a>). + + A <a for="/">service worker</a> has an associated <dfn export id="dfn-type">type</dfn> which is either "<code>classic</code>" or "<code>module</code>". Unless stated otherwise, it is "<code>classic</code>". + + A <a for="/">service worker</a> has an associated <dfn export id="dfn-containing-service-worker-registration" lt="registration|containing service worker registration">containing service worker registration</dfn> (a <a for="/">service worker registration</a>), which contains itself. + + A <a for="/">service worker</a> has an associated <dfn export id="dfn-service-worker-id">id</dfn> (an opaque string), which uniquely identifies itself during the lifetime of its <a>containing service worker registration</a>. + + A <a for="/">service worker</a> has an associated <dfn export id="dfn-service-worker-global-object" for="service worker">global object</dfn> (a {{ServiceWorkerGlobalScope}} object or null). + + A <a for="/">service worker</a> is dispatched a set of <dfn export id="dfn-lifecycle-events">lifecycle events</dfn>, <a event for="ServiceWorkerGlobalScope">install</a> and <a event for="ServiceWorkerGlobalScope">activate</a>, and <dfn export id="dfn-functional-events">functional events</dfn> including <a event for="ServiceWorkerGlobalScope">fetch</a>. Let's use `{{install!!event}}`. I think it'd not be ambiguous without the event target within the spec. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/ServiceWorker/pull/1014
Received on Wednesday, 30 November 2016 01:11:23 UTC