Closed Bug 1934993 Opened 2 months ago Closed 2 months ago

[wpt-sync] Sync PR 49501 - Reland "Enable 5 Protected Audience and Fenced Frame features in Mode A/B"

Categories

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

task

Tracking

(firefox135 fixed)

RESOLVED FIXED
135 Branch
Tracking Status
firefox135 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Paul Jensen <pauljensen@chromium.org> wrote:

Reland "Enable 5 Protected Audience and Fenced Frame features in Mode A/B"

This reverts commit b550c350a6ac01554b5d25c999d8d58b9389f289.

Reason for revert: Turned out to not be the cause of b/381980101 and
b/381977849 as they continued after the revert, and look to be WPT
cross-talk for which mitigations are already in progress (e.g.
https://crrev.com/1388378)

Original change's description:

Revert "Enable 5 Protected Audience and Fenced Frame features in Mode A/B"

This reverts commit 7f52df769dac418870a2d2a8fcd3f7c1f114405b.

Reason for revert: suspected culprit for b/381980101 and b/381977849

Bug: 381980101, 381977849

Original change's description:

Enable 5 Protected Audience and Fenced Frame features in Mode A/B

With the end of the Chrome-facilitated testing period, enable these features
in Modes A and B to provide a more consistent developer experience and
decrease the need for feature detection:

  • PA Real Time Reporting
  • PA multi-bid support
  • PA deprecatedReplaceInURN via auction config
  • PA multiple bidding contexts optimization
  • FF allow cross-origin subframes to send reportEvent() beacons

This was announced here:
https://groups.google.com/a/chromium.org/g/blink-dev/c/WgGGPElrG9o

Change-Id: I7d26fb1ea908837557bf60cc8762245c409d0160
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6049396
Auto-Submit: Paul Jensen \<pauljensen@chromium.org>
Reviewed-by: Shivani Sharma \<shivanisha@chromium.org>
Reviewed-by: Nasko Oskov \<nasko@chromium.org>
Commit-Queue: Nasko Oskov \<nasko@chromium.org>
Reviewed-by: Maks Orlovich \<morlovich@chromium.org>
Reviewed-by: Kent Tamura \<tkent@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1390666}

Change-Id: I4cf77749fb95b8de9cdc412c674f7edb9c481edd
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6062886
Auto-Submit: Florian Jacky \<fjacky@chromium.org>
Reviewed-by: Balazs Engedy \<engedy@chromium.org>
Bot-Commit: Rubber Stamper \<rubber-stamper@appspot.gserviceaccount.com>
Owners-Override: Florian Jacky \<fjacky@chromium.org>
Commit-Queue: Balazs Engedy \<engedy@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1390874}

Bug: 381980101, 381977849
Change-Id: Ia963eac7362df95567f48fd8c0a4c07127df73d2

Reviewed-on: https://chromium-review.googlesource.com/6065414
WPT-Export-Revision: 237b8c6ccdcfdcc65c679e65f5ac79f5e7776833

CI Results

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

Total 8 tests and 4 subtests

Status Summary

Firefox

OK : 8
FAIL: 31

Chrome

OK : 8
FAIL: 31

Safari

OK : 8
FAIL: 31

Links

GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

  • /fledge/tentative/generate-bid-browser-signals.https.window.html?25-28 [wpt.fyi]
    • browserSignals.prevWinsMs has only one win when winning ad used twice.: FAIL (Chrome: FAIL, Safari: FAIL)
    • browserSignals.prevWinsMs not updated when another interest group wins.: FAIL (Chrome: FAIL, Safari: FAIL)
    • browserSignals.prevWinsMs not updated when seller rejects bid.: FAIL (Chrome: FAIL, Safari: FAIL)
    • browserSignals.prevWinsMs not updated when seller throws.: FAIL (Chrome: FAIL, Safari: FAIL)
  • /fledge/tentative/generate-bid-browser-signals.https.window.html?9-12 [wpt.fyi]
    • browserSignals.bidCount leave and rejoin.: FAIL (Chrome: FAIL, Safari: FAIL)
    • browserSignals.bidCount two auctions at once.: FAIL (Chrome: FAIL, Safari: FAIL)
    • browserSignals.bidCount incremented once when winning ad used twice.: FAIL (Chrome: FAIL, Safari: FAIL)
    • browserSignals.bidCount incremented when another interest group wins.: FAIL (Chrome: FAIL, Safari: FAIL)
  • /fledge/tentative/generate-bid-browser-signals.https.window.html?13-16 [wpt.fyi]
    • browserSignals.bidCount incremented when seller rejects bid.: FAIL (Chrome: FAIL, Safari: FAIL)
    • browserSignals.bidCount incremented when seller throws.: FAIL (Chrome: FAIL, Safari: FAIL)
    • browserSignals.bidCount not incremented when no bid.: FAIL (Chrome: FAIL, Safari: FAIL)
    • browserSignals.bidCount not incremented when no bid and another interest group wins.: FAIL (Chrome: FAIL, Safari: FAIL)
  • /fledge/tentative/generate-bid-browser-signals.https.window.html?29-last [wpt.fyi]
    • browserSignals.prevWinsMs not updated when no bid.: FAIL (Chrome: FAIL, Safari: FAIL)
    • browserSignals.prevWinsMs not updated when makes largest bid, but another interest group wins.: FAIL (Chrome: FAIL, Safari: FAIL)
    • browserSignals.wasmHelper.: FAIL (Chrome: FAIL, Safari: FAIL)
  • /fledge/tentative/generate-bid-browser-signals.https.window.html?21-24 [wpt.fyi]
    • browserSignals.prevWinsMs, different set of ads for each bid.: FAIL (Chrome: FAIL, Safari: FAIL)
    • browserSignals.prevWinsMs persists across re-join from other top-level origin.: FAIL (Chrome: FAIL, Safari: FAIL)
    • browserSignals.prevWinsMs leave and rejoin.: FAIL (Chrome: FAIL, Safari: FAIL)
    • browserSignals.prevWinsMs two auctions at once.: FAIL (Chrome: FAIL, Safari: FAIL)
  • /fledge/tentative/generate-bid-browser-signals.https.window.html?17-20 [wpt.fyi]
    • browserSignals.bidCount incremented when makes largest bid, but seller rejects the bid.: FAIL (Chrome: FAIL, Safari: FAIL)
    • browserSignals.prevWinsMs not affected when ad not used.: FAIL (Chrome: FAIL, Safari: FAIL)
    • browserSignals.prevWinsMs, no metadata.: FAIL (Chrome: FAIL, Safari: FAIL)
    • browserSignals.prevWinsMs, with metadata.: FAIL (Chrome: FAIL, Safari: FAIL)
  • /fledge/tentative/generate-bid-browser-signals.https.window.html?5-8 [wpt.fyi]
    • Check recency in generateBid() is below a certain threshold and rounded to multiple of 100 milliseconds.: FAIL (Chrome: FAIL, Safari: FAIL)
    • browserSignals.bidCount not incremented when ad not used.: FAIL (Chrome: FAIL, Safari: FAIL)
    • browserSignals.bidCount incremented when ad used.: FAIL (Chrome: FAIL, Safari: FAIL)
    • browserSignals.bidCount persists across re-join from other top-level origin.: FAIL (Chrome: FAIL, Safari: FAIL)
  • /fledge/tentative/generate-bid-browser-signals.https.window.html?1-4 [wpt.fyi]
    • Only expected fields present.: FAIL (Chrome: FAIL, Safari: FAIL)
    • browserSignals.joinCount same joining page.: FAIL (Chrome: FAIL, Safari: FAIL)
    • browserSignals.joinCount different top-level joining origin.: FAIL (Chrome: FAIL, Safari: FAIL)
    • browserSignals.joinCount leave and rejoin.: FAIL (Chrome: FAIL, Safari: FAIL)
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/c3d46da20ac3 [wpt PR 49501] - Reland "Enable 5 Protected Audience and Fenced Frame features in Mode A/B", a=testonly
Status: NEW → RESOLVED
Closed: 2 months ago
Resolution: --- → FIXED
Target Milestone: --- → 135 Branch
You need to log in before you can comment on or make changes to this bug.