Reland "Fenced frame: Fix some WPTs in headless mode." (#48701)
The original CL was crashing in an instance where multiClick() was
invoked without an await. This fixes the crash by awaiting the clicks
instead of continuing with/finishing the test before all the clicks
have propagated inside navigate-ancestor-test-runner.https.html.
Original change's description:
Fenced frame: Fix some WPTs in headless mode.
There is currently a push to allow Chromium web platform tests to run
in headless mode (i.e. without a content shell). This requires some
changes to how fenced frame tests work. Headless mode does not support
test_driver functions from inside of fenced frames, as those require
access to the main frame's window to pass the message onto, which
fenced frames deliberately block for privacy reasons. This CL fixes
some of the tests that fail in headless mode by moving those
test_driver calls to the main frame, specifically clicking actions
(which we already have multiClick() to handle this in main frames),
and set_permission().See the headless mode explainer:
https://chromium.googlesource.com/chromium/src/+/HEAD/headless/README.mdChange-Id: Iab82a581b67f8f8851c7716a2d72caf566f3b2ae
Bug: 366257368
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5935060
Reviewed-by: Andrew Verge averge@chromium.org
Commit-Queue: Liam Brady lbrady@google.com
Cr-Commit-Position: refs/heads/main@{#1370151}
Bug: 366257368
Change-Id: Id998687c2f3de41a7b0dcd5197ba74fb22ef979e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5938155
Reviewed-by: Andrew Verge averge@chromium.org
Commit-Queue: Liam Brady lbrady@google.com
Cr-Commit-Position: refs/heads/main@{#1370703}
Co-authored-by: Liam Brady lbrady@google.com