[wpt-sync] Sync PR 12263 - [Background Fetch] Reject BackgroundFetchUpdateEvent::UpdateUI if called again

RESOLVED FIXED in Firefox 63

Status

()

enhancement
P4
normal
RESOLVED FIXED
Last year
11 months ago

People

(Reporter: wptsync, Unassigned)

Tracking

unspecified
mozilla63
Points:
---

Firefox Tracking Flags

(firefox63 fixed)

Details

(Whiteboard: [wptsync downstream], )

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

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

Rayan Kanso <rayankans@chromium.org> wrote:
>  [Background Fetch] Reject BackgroundFetchUpdateEvent::UpdateUI if called again
>  
>  Also add layout tests.
>  
>  Change-Id: I4b8e1847a09fd84a087d4f4af996ccf19c9f212b
>  Reviewed-on: https://chromium-review.googlesource.com/1159073
>  WPT-Export-Revision: ac363f44d65ea2c6c02a97f2fa536b0a2c6c7282
Component: web-platform-tests → DOM: Service Workers
Product: Testing → Core
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Ran 8 tests and 32 subtests
OK     : 8
FAIL   : 32

New tests that have failures or other problems:
/background-fetch/update-ui.https.window.html
    Background Fetch updateUI called twice fails: FAIL
    Background Fetch updateUI resolves: FAIL
Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/a4f967c85a74
[wpt PR 12263] - [Background Fetch] Reject BackgroundFetchUpdateEvent::UpdateUI if called again, a=testonly
https://hg.mozilla.org/integration/mozilla-inbound/rev/d6082096a036
[wpt PR 12263] - Update wpt metadata, a=testonly
https://hg.mozilla.org/mozilla-central/rev/a4f967c85a74
https://hg.mozilla.org/mozilla-central/rev/d6082096a036
Status: NEW → RESOLVED
Closed: 11 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla63
You need to log in before you can comment on or make changes to this bug.