Closed Bug 1778011 Opened 2 years ago Closed 2 years ago

[wpt-sync] Sync PR 34694 - Add and wire up bfcache restoration entry

Categories

(Core :: Performance, task, P4)

task

Tracking

()

RESOLVED FIXED
106 Branch
Performance Impact none
Tracking Status
firefox106 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(Depends on 1 open bug, )

Details

(Whiteboard: [wptsync downstream error])

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

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

Hao Liu <haoliuk@chromium.org> wrote:

Add and wire up bfcache restoration entry

The BackForwardCacheRestorationEntry is a new type of PerformanceEntry. One instance of this will be created each time there is a back/forward cache navigation.

The new entry is supported both by performance observer and performance timeline API.

Change-Id: I11b043f76c67a6638a44274ace8ef001af796a41
Reviewed-on: https://chromium-review.googlesource.com/3714558
WPT-Export-Revision: a9d63311875df12eabf2f3c02bea5985dea61236

Component: web-platform-tests → Performance
Product: Testing → Core
Performance Impact: --- → -
Component: Performance → DOM: Performance
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Component: DOM: Performance → Performance

CI Results

Ran 0 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI

Total 1 tests and 1 subtests

Status Summary

Firefox

TIMEOUT: 2

Chrome

TIMEOUT: 2

Safari

TIMEOUT: 2

Links

GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/a4be86b7ae5e [wpt PR 34694] - Add and wire up bfcache restoration entry, a=testonly https://hg.mozilla.org/integration/autoland/rev/f55cce3be2a2 [wpt PR 34694] - Update wpt metadata, a=testonly
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 106 Branch
You need to log in before you can comment on or make changes to this bug.