Closed Bug 1842552 Opened 1 year ago Closed 1 year ago

[wpt-sync] Sync PR 40941 - Reland "[soft navigations] Block FP and FCP entries behind a flag"

Categories

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

task

Tracking

(firefox117 fixed)

RESOLVED FIXED
117 Branch
Tracking Status
firefox117 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Yoav Weiss <yoavweiss@chromium.org> wrote:

Reland "[soft navigations] Block FP and FCP entries behind a flag"

This is a reland of commit caf3834a5cb3e46c2bdb6c18bd48f066eafd0145

Original change's description:

[soft navigations] Block FP and FCP entries behind a flag

Bug: 1457049
Change-Id: I3065b5941f89cedb8ee0df3331a5adaf9415b84d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4665521
Reviewed-by: Ian Clelland \<iclelland@chromium.org>
Commit-Queue: Yoav Weiss \<yoavweiss@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1166497}

Bug: 1457049
Change-Id: I4ef2b65c1f009c30fa17bbce8957dc85565babe4

Reviewed-on: https://chromium-review.googlesource.com/4674335
WPT-Export-Revision: 63bda60d2abbc6f6200b8eb88607e3725741ff32

CI Results

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

Total 28 tests and 1 subtests

Status Summary

Firefox

OK : 7
PASS : 1
FAIL : 6
TIMEOUT: 34
ERROR : 4

Chrome

OK : 28
PASS : 28

Safari

OK : 6
PASS : 1
FAIL : 5
TIMEOUT: 36
ERROR : 4

Links

Gecko CI (Treeherder)
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/51eb7afdc2e0 [wpt PR 40941] - Reland "[soft navigations] Block FP and FCP entries behind a flag", a=testonly
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 117 Branch
You need to log in before you can comment on or make changes to this bug.