1871076 - [wpt-sync] Sync PR 43754 - Fenced frame: Add ad component remote context WPT support.

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 43754 into mozilla-central (this bug is closed when the sync is complete).

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

Liam Brady <[e-mail]> wrote:

Fenced frame: Add ad component remote context WPT support.

Introduces a way to embed ad components within frames and be able to run
arbitrary JavaScript in them.

Steps for setting up:

1. Create a fenced frame or URN iframe remote context using either
   attachFencedFrameContext() or attachIFrameContext(). Specify the new
   include_component: true parameter when calling the function. This
   will create a remote context URL/URN, but not actually create a frame.
2. To create the ad component frame, call either
   attachComponentFencedFrameContext() or attachComponentIFrameContext().
   This will construct an ad component frame, and return the remote context
   object the same way that attachFencedFrameContext/attachIFrameContext
   does. This can be interacted with in the same way that any other remote
   context frame can be interacted with.

As a proof of concept, this CL makes the following test changes:

1. Updates nested-opaque-ad-sizes.https.html to finally be functional.
2. Adds a WPT to test that ad components can send automatic beacons with
   a header opt-in.

Change-Id: Ic4277b4082e36617f95f20895c9502bca3928965
Bug: 1427455

Reviewed-on: https://chromium-review.googlesource.com/5136743
WPT-Export-Revision: 1705360cba5deff2789828eb38e53adb5383c75e

Comment 1

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

Pushed to try (stability) https://treeherder.mozilla.org/#/jobs?repo=try&revision=1a2aaec8e7ec8d6adf4c035b9fb211a39380308d

Comment 2

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

Attachment: Notable wpt changes

# CI Results

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

Total 211 tests and 1 subtests

## Status Summary

### Firefox
`OK`     : 190
`PASS`   : 23
`FAIL`   : 510
`TIMEOUT`: 30
`ERROR`  : 8
`NOTRUN` : 21

### Chrome
`OK`     : 190
`PASS`   : 24
`FAIL`   : 513
`TIMEOUT`: 30
`ERROR`  : 8
`NOTRUN` : 17

### Safari
`OK`     : 189
`PASS`   : 22
`FAIL`   : 509
`TIMEOUT`: 30
`ERROR`  : 9
`NOTRUN` : 21

## Links
[GitHub PR Head](https://wpt.fyi/results/?sha=0f8b3844eee507d063d9e3c0be06864092b1aa3c&label=pr_head)
[GitHub PR Base](https://wpt.fyi/results/?sha=0f8b3844eee507d063d9e3c0be06864092b1aa3c&label=pr_base)

## Details

(See attachment for full changes)

Comment 3

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/aca6c5d598f1
[wpt PR 43754] - Fenced frame: Add ad component remote context WPT support., a=testonly
https://hg.mozilla.org/integration/autoland/rev/5b9f56b286d9
[wpt PR 43754] - Update wpt metadata, a=testonly

Comment 4

[Serban Stanca [:SerbanS]]

https://hg.mozilla.org/mozilla-central/rev/aca6c5d598f1
https://hg.mozilla.org/mozilla-central/rev/5b9f56b286d9