1865912 - [wpt-sync] Sync PR 43271 - Fenced frames: Fix reportEvent request initiator

Status: RESOLVED FIXED

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

Description

[Web Platform Test Sync Bot [:wpt-sync] (Matrix: #interop:mozilla.org)]

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

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

Garrett Tanzer <[e-mail]> wrote:

Fenced frames: Fix reportEvent request initiator

The request initiator for beacons is now whoever chose the destination
URL:

• For destination enum beacons (including all automatic beacons), this
  is the reporting worklet's origin.
• For destination URL beacons (with macro substitution), this is the
  reportEvent caller's origin.

Bug: 1498474
Change-Id: I426ac8a05f8c197669df72fb6a82394029993029
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5037514
Reviewed-by: Dominic Farolino \<[e-mail]>
Reviewed-by: Matt Menke \<[e-mail]>
Commit-Queue: Garrett Tanzer \<[e-mail]>
Cr-Commit-Position: refs/heads/main@{#1227504}

Comment 1

[Web Platform Test Sync Bot [:wpt-sync] (Matrix: #interop:mozilla.org)]

CI Results

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

Total 7 tests

Status Summary

Firefox

OK : 6
FAIL : 6
ERROR: 1

Chrome

OK : 6
FAIL : 6
ERROR: 1

Safari

OK : 6
FAIL : 6
ERROR: 1

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

• /fenced-frame/automatic-beacon-anchor-click-handler.https.html [wpt.fyi]
  • Set and trigger an automatic beacon in an <a> click handler: FAIL (Chrome: FAIL, Safari: FAIL)
• /fenced-frame/automatic-beacon-click-handler.https.html [wpt.fyi]
  • Set and trigger an automatic beacon in a click handler: FAIL (Chrome: FAIL, Safari: FAIL)
• /fenced-frame/automatic-beacon-no-destination.https.html [wpt.fyi]
  • Set and trigger an automatic beacon with no destination specified: FAIL (Chrome: FAIL, Safari: FAIL)
• /fenced-frame/automatic-beacon-shared-storage.https.html [wpt.fyi]
  • Set and trigger an automatic beacon in a click handler for SharedStorage: FAIL (Chrome: FAIL, Safari: FAIL)
• /fenced-frame/automatic-beacon-two-events-clear.https.html [wpt.fyi]
  • Set expiring automatic beacon but trigger two events in a click handler: FAIL (Chrome: FAIL, Safari: FAIL)
• /fenced-frame/automatic-beacon-two-events-persist.https.html [wpt.fyi]
  • Set persisting automatic beacon but trigger two events in a click handler: FAIL (Chrome: FAIL, Safari: FAIL)
• /fenced-frame/automatic-beacon-unfenced-top.https.html [wpt.fyi]: ERROR (Chrome: ERROR, Safari: ERROR)

Comment 2

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/ae8a62684da1
[wpt PR 43271] - Fenced frames: Fix reportEvent request initiator, a=testonly

Comment 3

[Pulsebot]

Backout by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/ffaaa99c5172
Backed out 46 changesets (bug 1865912, bug 1865927, bug 1865071, bug 1865839, bug 1865237, bug 1865718, bug 1863796, bug 1865834, bug 1865970, bug 1864254, bug 1865836, bug 1865688, bug 1865971, bug 1865493, bug 1865669, bug 1865944, bug 1865923, bug 1865682, bug 1865832, bug 1864024, bug 1865833, bug 1865842, bug 1865646, bug 1865579, bug 1865434, bug 1864668, bug 1865584, bug 1865949, bug 1865553, bug 1864854, bug 1865925, bug 1865583, bug 1865580, bug 1865710, bug 1865350, bug 1861916, bug 1866167, bug 1864974) for causing spidermonkey bustages CLOSED TREE

Comment 4

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/216ccaa2ebd4
[wpt PR 43271] - Fenced frames: Fix reportEvent request initiator, a=testonly

Comment 5

[Iulian Moraru]

https://hg.mozilla.org/mozilla-central/rev/216ccaa2ebd4