Closed Bug 1527719 Opened 5 years ago Closed 5 years ago

[wpt-sync] Sync PR 15359 - KV storage: make backingStore return the same frozen object

Categories

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

Product:
Testing
Component:
web-platform-tests
Type:
enhancement

Tracking

(firefox67 fixed)

Status:
RESOLVED FIXED
Milestone:
mozilla67
Tracking Flags:
Tracking Status
firefox67 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

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

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

Domenic Denicola <domenic@chromium.org> wrote:

KV storage: make backingStore return the same frozen object

Follows https://github.com/WICG/kv-storage/pull/51.

Bug: 931263
Change-Id: Ia3b1482093bfaca443b8809c6e284397fdb6fec1
Reviewed-on: https://chromium-review.googlesource.com/1466863
WPT-Export-Revision: 9306ee73c87e50342c44fb9617ec037dc0791116

Ran 2 tests
TIMEOUT: 2

New tests that have failures or other problems:
/kv-storage/backingstore.https.html: TIMEOUT
Pushed by james@hoppipolla.co.uk:
https://hg.mozilla.org/integration/mozilla-inbound/rev/1fb1b5a75a79
[wpt PR 15359] - KV storage: make backingStore return the same frozen object, a=testonly
https://hg.mozilla.org/integration/mozilla-inbound/rev/e5f7bd9d93a4
[wpt PR 15359] - Update wpt metadata, a=testonly
Pushed by james@hoppipolla.co.uk:
https://hg.mozilla.org/integration/mozilla-inbound/rev/f5dcec1e551e
[wpt PR 15359] - KV storage: make backingStore return the same frozen object, a=testonly
https://hg.mozilla.org/integration/mozilla-inbound/rev/db9008086741
[wpt PR 15359] - Update wpt metadata, a=testonly

https://hg.mozilla.org/mozilla-central/rev/f5dcec1e551e
https://hg.mozilla.org/mozilla-central/rev/db9008086741

Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox67: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla67
You need to log in before you can comment on or make changes to this bug.