Closed Bug 1873116 Opened 2 years ago Closed 2 years ago

[wpt-sync] Sync PR 43860 - [wptrunner] Rewrite `test_win_open_with_interaction.html`

Categories

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

task

Tracking

(firefox123 fixed)

RESOLVED FIXED
123 Branch
Tracking Status
firefox123 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Jonathan Lee <jonathanjlee@google.com> wrote:

[wptrunner] Rewrite test_win_open_with_interaction.html

This test didn't work as intended for testdriver.js implemented with
WebDriver because of crbug.com/1453780#c8. Fix the test page to also
include testdriver.js, and rewrite the test as an equivalent
promise_test(...) that performs interaction like the closely related
infrastructure/testdriver/actions/crossOrigin.sub.html 0.

The test now passes for chrome and other WebDriver-enabled browsers,
but content_shell still delivers events to the wrong window.

Bug: 1453780
Change-Id: Iaaf33a7cbbccd8c63acfd5e68e6ea76954c520fd
Reviewed-on: https://chromium-review.googlesource.com/5171750
WPT-Export-Revision: 87da470c74f6fb56008beca90e07b1a21f57356e

CI Results

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

Total 2 tests and 1 subtests

Status Summary

Firefox

OK : 2
PASS: 2

Chrome

OK : 2
PASS: 1
FAIL: 1

Safari

OK : 2
PASS: 2

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/723cf873cd42 [wpt PR 43860] - [wptrunner] Rewrite `test_win_open_with_interaction.html`, a=testonly https://hg.mozilla.org/integration/autoland/rev/2007d88f92d7 [wpt PR 43860] - Update wpt metadata, a=testonly
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 123 Branch
You need to log in before you can comment on or make changes to this bug.