Closed Bug 1464503 Opened Last year Closed Last year

[wpt-sync] Sync PR 11165 - [PageLifecycle] Add WPT test for lifecycle's onfreeze callback

Categories

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

enhancement

Tracking

(firefox62 fixed)

RESOLVED FIXED
mozilla62
Tracking Status
firefox62 --- fixed

People

(Reporter: wptsync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Fadi Meawad <fmeawad@chromium.org> wrote:
>  [PageLifecycle] Add WPT test for lifecycle's onfreeze callback
>  
>  Since the onfreeze callback is invoked based on an internal decision
>  from the browser, to be able to test the callback, we are adding support
>  for it from chromeGPUBenchmak as well as in chromedriver/WebDriver.
>  
>  This CL focuses on the chromeGPUBenchmark solution.
>  
>  The WPT test itself, verifies that the onfreeze callback is called, and
>  it also verifies that only fetch keepalive is allowed from withing the
>  callback.
>  
>  Bug:chromium:837709
>  Change-Id: Ia4cb16dc10625f478ec270617da1a26395a9d29d
>  Reviewed-on: https://chromium-review.googlesource.com/1072899
>  WPT-Export-Revision: 8171102d7d9c0509eea71455b4f6e8e9966abd2c
Ran 183 tests and 229 subtests
OK     : 167
PASS   : 12
FAIL   : 175
TIMEOUT: 33
ERROR  : 10
NOTRUN : 15

New tests that have failures or other problems:
/lifecycle/freeze.html
    Test freeze callback.: FAIL
Pushed by james@hoppipolla.co.uk:
https://hg.mozilla.org/integration/mozilla-inbound/rev/e5cf8dad80f0
[wpt PR 11165] - [PageLifecycle] Add WPT test for lifecycle's onfreeze callback, a=testonly
https://hg.mozilla.org/integration/mozilla-inbound/rev/05c9b364a0db
[wpt PR 11165] - Update wpt metadata, a=testonly
https://hg.mozilla.org/mozilla-central/rev/e5cf8dad80f0
https://hg.mozilla.org/mozilla-central/rev/05c9b364a0db
Status: NEW → RESOLVED
Closed: Last year
Resolution: --- → FIXED
Target Milestone: --- → mozilla62
You need to log in before you can comment on or make changes to this bug.