Closed Bug 1793701 Opened 2 years ago Closed 2 years ago

[wpt-sync] Sync PR 36275 - Revert "[bfcache] Add notRestoredReasons field in PerformanceNavigationTiming"

Categories

(Core :: DOM: Core & HTML, 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 36275 into mozilla-central (this bug is closed when the sync is complete).

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

Emily Shack <emshack@chromium.org> wrote:

Revert "[bfcache] Add notRestoredReasons field in PerformanceNavigationTiming"

This reverts commit e1af9facf232a11871b0c668b90ec17c5a5d5e16.

Reason for revert: Likely cause for multiple builder failures. For example, see https://ci.chromium.org/ui/p/chromium/builders/ci/Linux%20ASan%20Tests%20(sandboxed)/93643/overview

Original change's description:

[bfcache] Add notRestoredReasons field in PerformanceNavigationTiming

This CL adds back/forward cache not restored reasons in Performance
NavigationTiming API.
It's proposed here:
https://github.com/w3c/navigation-timing/issues/171
Explainer: https://github.com/rubberyuzu/bfcache-not-retored-reason/blob/main/NotRestoredReason.md

This CL does two things:

  • exposes not restored reasons to PerformanceNavigationTiming API
  • adds WPT

The WPT have to run on all platforms because this API is intended to
collect bfcache metrics from the wild, regardless of the platforms.

LOW_COVERAGE_REASON=Adding coverage for new field. Just missing the tests for the existing fields

Bug: 1349228
Change-Id: I8dd96a60188bdff94a21c4e4e34cacf181a823db
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3835534
Reviewed-by: Daniel Cheng \<dcheng@chromium.org>
Reviewed-by: Kentaro Hara \<haraken@chromium.org>
Reviewed-by: Weizhong Xia \<weizhong@google.com>
Commit-Queue: Yuzu Saijo \<yuzus@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1054800}

Bug: 1349228
Change-Id: Iab0fed375560bb0b09bf4e8ea18b80c5d88b1375
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3935464
Owners-Override: Emily Shack \<emshack@google.com>
Reviewed-by: Kentaro Hara \<haraken@chromium.org>
Commit-Queue: Kentaro Hara \<haraken@chromium.org>
Auto-Submit: Emily Shack \<emshack@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1055015}

PR 36275 applied with additional changes from upstream: 88c0d4ec3d12f5389297f08ced7785e2c402cf36
Component: web-platform-tests → DOM: Core & HTML
Product: Testing → Core

CI Results

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

Total 15 tests and 1 subtests

Status Summary

Firefox

OK : 15
PASS: 15

Chrome

OK : 15
PASS: 15

Safari

OK : 15
PASS: 15

Links

GitHub PR Head
GitHub PR Base

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/1217e1e14a2f [wpt PR 36275] - Revert "[bfcache] Add notRestoredReasons field in PerformanceNavigationTiming", a=testonly
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 108 Branch
You need to log in before you can comment on or make changes to this bug.