Closed Bug 2036707 Opened 13 days ago Closed 9 days ago

[wpt-sync] Sync PR 59587 - Remove window.fence.notifyEvent and associated code.

Categories

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

task

Tracking

(firefox152 fixed)

RESOLVED FIXED
152 Branch
Tracking Status
firefox152 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Andrew Verge <averge@chromium.org> wrote:

Remove window.fence.notifyEvent and associated code.

This API was added as part of the Fenced Storage Read feature,
which is no longer launching. This CL cleans up the implementation
in Blink and content/, as well as associated WPTs and histograms.
It also removes the FencedFrameViewportObserver, which was only
necessary due to the existence of notifyEvent.

OBSOLETE_HISTOGRAMS=fence.notifyEvent API is being removed, so features related to its use no longer need to be tracked.

Bug: 499191497
Change-Id: I337de9e8b902a1927a99798d69acfdc8d990674d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7804730
Reviewed-by: Alex Moshchuk \<alexmos@chromium.org>
Reviewed-by: Kevin Graney \<kmg@google.com>
Commit-Queue: Andrew Verge \<averge@chromium.org>
Reviewed-by: Xiaochen Zhou \<xiaochenzh@chromium.org>
Reviewed-by: Dominic Farolino \<dom@chromium.org>
Reviewed-by: Yi Gu \<yigu@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1623661}

The PR was not expected to affect any tests, but the try push wasn't a success. Check the try results for infrastructure issues

Pushed by wptsync@mozilla.com: https://github.com/mozilla-firefox/firefox/commit/a19da578fa06 https://hg.mozilla.org/integration/autoland/rev/5ef70281c512 [wpt PR 59587] - Remove window.fence.notifyEvent and associated code., a=testonly
Status: NEW → RESOLVED
Closed: 9 days ago
Resolution: --- → FIXED
Target Milestone: --- → 152 Branch
You need to log in before you can comment on or make changes to this bug.