Closed Bug 1795465 Opened 3 years ago Closed 3 years ago

[wpt-sync] Sync PR 36464 - Verify navigation id existence.

Categories

(Core :: DOM: Performance APIs, task, P4)

task

Tracking

()

RESOLVED FIXED
108 Branch
Tracking Status
firefox108 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Hao Liu <haoliuk@chromium.org> wrote:

Verify navigation id existence.

Navigation timing, LCP and paint timing entries are not emitted
after a bfcache navigation. Therefore we only verify the
existence of navigation id, not the increment.

Bug: 1320878
Change-Id: I0eb4568d9418b70ff625f783430de7ae1205b091
Reviewed-on: https://chromium-review.googlesource.com/3956481
WPT-Export-Revision: b3bf65c3358a47c1eb2cb492d0a6c5ec128dbe8d

Component: web-platform-tests → DOM: Performance
Product: Testing → Core

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

OK : 1
PASS : 1

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/e5eb2ca09856 [wpt PR 36464] - Verify navigation id existence., a=testonly https://hg.mozilla.org/integration/autoland/rev/990e75eb12d9 [wpt PR 36464] - Update wpt metadata, a=testonly
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 108 Branch
You need to log in before you can comment on or make changes to this bug.