Closed Bug 1845729 Opened 1 year ago Closed 1 year ago

[wpt-sync] Sync PR 41204 - Make FencedFrameConfigs serializable.

Categories

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

Product:
Testing
Component:
web-platform-tests
Type:
task

Tracking

(firefox118 fixed)

Status:
RESOLVED FIXED
Milestone:
118 Branch
Tracking Flags:
Tracking Status
firefox118 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

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

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

Liam Brady <lbrady@google.com> wrote:

Make FencedFrameConfigs serializable.

There is a use case where a FencedFrameConfig object is created inside
of a cross-origin iframe, and then passed to its embedder via
postMessage() to load in a fenced frame. To support that, this CL makes
the FencedFrameConfig object serializable, which allows it to be deep
copied through structuredClone() or sent as a message in postMessage().

Change-Id: I5bfc1d12d813790e767b992f2561167719833035

Reviewed-on: https://chromium-review.googlesource.com/4721701
WPT-Export-Revision: 15a00ab8fc59f9770309aefea599b4f3e65dad08

Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]

CI Results

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

Total 1 tests and 4 subtests

Status Summary

Firefox

OK : 1
FAIL: 4

Chrome

OK : 1
FAIL: 4

Safari

OK : 1
FAIL: 4

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

  • /fenced-frame/deep-copy-config.https.html [wpt.fyi]
    • A cloned config with a URN will navigate.: FAIL (Chrome: FAIL, Safari: FAIL)
    • A cloned config with a URL will navigate.: FAIL (Chrome: FAIL, Safari: FAIL)
    • A config received through window.postMessage will navigate.: FAIL (Chrome: FAIL, Safari: FAIL)
    • A FencedFrameConfig cannot be written to storage.: FAIL (Chrome: FAIL, Safari: FAIL)
Pushed by ctuns@mozilla.com:
https://hg.mozilla.org/mozilla-central/rev/0ec14b7000d6
[wpt PR 41204] - Make FencedFrameConfigs serializable., a=testonly
https://hg.mozilla.org/mozilla-central/rev/4f3380ef0434
[wpt PR 41204] - Update wpt metadata, a=testonly

https://hg.mozilla.org/mozilla-central/rev/0ec14b7000d6
https://hg.mozilla.org/mozilla-central/rev/4f3380ef0434

Status: NEW → RESOLVED
Closed: 1 year ago
status-firefox118: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 118 Branch
You need to log in before you can comment on or make changes to this bug.