[wpt-sync] Sync PR 46325 - Use boolean in cross-origin reportEvent() opt in header.
Categories
(Core :: DOM: Core & HTML, task, P4)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox128 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 46325 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/46325
Details from upstream follow.
Liam Brady <lbrady@google.com> wrote:
Use boolean in cross-origin reportEvent() opt in header.
The opt in header currently expects the string literal "true" to opt
the fenced frame's config into being used for reportEvent() calls
originating from cross-origin subframes. Using string literals are an
outdated syntax. Instead, the current spec prefers using the boolean
values "?0" and "?1". This CL updates the header to expect a boolean.The feature has not shipped yet, so there is no need for backwards
compatibility for the existing syntax.Change-Id: I2d2aea9713b98acb6984f7c57971413fe684afb3
Bug: 331844131Reviewed-on: https://chromium-review.googlesource.com/5542760
WPT-Export-Revision: 487c7eb24eaccd0d6dd2d426619dd97ce8943663
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Comment 1•1 year ago
|
||
| Assignee | ||
Comment 2•1 year ago
|
||
CI Results
Ran 0 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI
Total 11 tests and 1 subtests
Status Summary
Firefox
OK : 11
FAIL : 11
Chrome
OK : 6
FAIL : 6
TIMEOUT: 10
Safari
OK : 11
FAIL : 11
Links
Details
New Tests That Don't Pass
- /fenced-frame/fence-report-event-cross-origin-content-initiated.https.html [wpt.fyi]
- window.fence.reportEvent from a content-initiated cross-origin navigation:
FAIL(Chrome:FAIL, Safari:FAIL)
- window.fence.reportEvent from a content-initiated cross-origin navigation:
- /fenced-frame/fence-report-event-cross-origin-nested-urn-iframe.https.html [wpt.fyi]
- window.fence.reportEvent from a nested cross-origin subframe of a URN iframe:
FAIL(Chrome:TIMEOUT, Safari:FAIL)
- window.fence.reportEvent from a nested cross-origin subframe of a URN iframe:
- /fenced-frame/fence-report-event-cross-origin-nested.https.html [wpt.fyi]
- window.fence.reportEvent from a nested cross-origin subframe:
FAIL(Chrome:FAIL, Safari:FAIL)
- window.fence.reportEvent from a nested cross-origin subframe:
- /fenced-frame/fence-report-event-cross-origin-no-embedder-opt-in.https.html [wpt.fyi]
- Cross-origin window.fence.reportEvent without embedder opt-in:
FAIL(Chrome:FAIL, Safari:FAIL)
- Cross-origin window.fence.reportEvent without embedder opt-in:
- /fenced-frame/fence-report-event-cross-origin-no-subframe-opt-in.https.html [wpt.fyi]
- Cross-origin window.fence.reportEvent without subframe opt-in:
FAIL(Chrome:FAIL, Safari:FAIL)
- Cross-origin window.fence.reportEvent without subframe opt-in:
- /fenced-frame/fence-report-event-cross-origin-urn-iframe-content-initiated.https.html [wpt.fyi]
- window.fence.reportEvent from a content-initiated cross-origin navigation:
FAIL(Chrome:TIMEOUT, Safari:FAIL)
- window.fence.reportEvent from a content-initiated cross-origin navigation:
- /fenced-frame/fence-report-event-cross-origin-urn-iframe-no-embedder-opt-in.https.html [wpt.fyi]
- Cross-origin window.fence.reportEvent without embedder opt-in:
FAIL(Chrome:TIMEOUT, Safari:FAIL)
- Cross-origin window.fence.reportEvent without embedder opt-in:
- /fenced-frame/fence-report-event-cross-origin-urn-iframe-no-subframe-opt-in.https.html [wpt.fyi]
- Cross-origin window.fence.reportEvent without subframe opt-in:
FAIL(Chrome:TIMEOUT, Safari:FAIL)
- Cross-origin window.fence.reportEvent without subframe opt-in:
- /fenced-frame/fence-report-event-cross-origin-urn-iframe.https.html [wpt.fyi]
- window.fence.reportEvent from a cross-origin iframe:
FAIL(Chrome:TIMEOUT, Safari:FAIL)
- window.fence.reportEvent from a cross-origin iframe:
- /fenced-frame/fence-report-event-cross-origin.https.html [wpt.fyi]
- window.fence.reportEvent from a cross-origin subframe:
FAIL(Chrome:FAIL, Safari:FAIL)
- window.fence.reportEvent from a cross-origin subframe:
- /fenced-frame/fence-report-event-sub-fencedframe.https.html [wpt.fyi]
- window.fence.reportEvent should not work in a nested fenced frame:
FAIL(Chrome:FAIL, Safari:FAIL)
- window.fence.reportEvent should not work in a nested fenced frame:
Description
•