[w3c/ServiceWorker] Improve Activate with Try Activate (#1065)

This adds concepts and algorithms to track events (all service worker
events: lifecycle events, functional events, extendable message events)
that have pending extension promises so they can be used to check if the
registration's waiting worker can be promoted.

This also changes Install algorithm and related steps to match to the
implementations behavior. That is, instead of waiting for the promotion
condition in Install algorithm, newly introduced Try Activate algorithm
just tries to activate depending on the condition and return. Try
Activate is called when:
 - A service worker is installed.
 - The last client controlled by the existing active worker is unloaded.
 - skipWaiting() is called.
 - The extend lifetime promises for the existing active worker settle.

Related issue: #916.
You can view, comment on, or merge this pull request online at:

  https://github.com/w3c/ServiceWorker/pull/1065

-- Commit Summary --

  * Improve Activate with Try Activate

-- File Changes --

    M docs/index.bs (91)
    M docs/index.html (566)
    M docs/v1/index.bs (82)
    M docs/v1/index.html (520)

-- Patch Links --

https://github.com/w3c/ServiceWorker/pull/1065.patch
https://github.com/w3c/ServiceWorker/pull/1065.diff

-- 
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/1065