Closed Bug 1583474 Opened 11 months ago Closed 10 months ago

[wpt-sync] Sync PR 19246 - Service worker: Add self.serviceWorker to ServiceWorkerGlobalScope

Categories

(Testing :: web-platform-tests, task, P4)

task

Tracking

(firefox71 fixed)

RESOLVED FIXED
mozilla71
Tracking Status
firefox71 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 19246 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/19246
Details from upstream follow.

Yuta Kasai <yutakasai@google.com> wrote:

Service worker: Add self.serviceWorker to ServiceWorkerGlobalScope

This CL adds "self.serviceWorker" to ServiceWorkerGlobalScope.

  • In the previous code, the expiration time isn't set property
    so that the service worker doesn't post messages to itself at the beginning.
    This CL sets max_request_expiration_time property in ServiceWorkerVersion::StartWorker.
  • In spec, service worker's initialize state should be parsed.
    https://w3c.github.io/ServiceWorker/#service-worker-concept

Bug: 977496
Change-Id: I4f8368e165fb84304b49519ed43d7b21d5ec756d

Reviewed-on: https://chromium-review.googlesource.com/1819091
WPT-Export-Revision: ce0bc7cc02034b5e756a1e0425ffb186db4f803c

## GitHub CI Results
wpt.fyi [PR Results](https://wpt.fyi/results/?sha=d8ff3ac4c8b60726745cacd5c07e3a2de27c14f0&label=pr_head) [Base Results](https://wpt.fyi/results/?sha=d8ff3ac4c8b60726745cacd5c07e3a2de27c14f0&label=pr_base)

Ran 1 tests and 4 subtests

### Firefox
  OK  : 1
  FAIL: 4

### Chrome
  OK  : 1
  FAIL: 4

### Safari
  OK  : 1
  FAIL: 4

## Gecko CI Results

Ran 1 tests and 4 subtests
  OK     : 1
  FAIL   : 4
Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/95e1f1809a29
[wpt PR 19246] - Service worker: Add self.serviceWorker to ServiceWorkerGlobalScope, a=testonly
Status: NEW → RESOLVED
Closed: 10 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla71
You need to log in before you can comment on or make changes to this bug.