Closed Bug 1932829 Opened 9 months ago Closed 9 months ago

[wpt-sync] Sync PR 49327 - [WebDriver BiDi] Align initial `browsingContext` events with the spec

Categories

(Remote Protocol :: WebDriver BiDi, task, P4)

task

Tracking

(firefox135 fixed)

RESOLVED FIXED
135 Branch
Tracking Status
firefox135 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(Blocks 1 open bug, )

Details

(Whiteboard: [wptsync downstream])

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

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

Maksim Sadym <sadym@chromium.org> wrote:

[WebDriver BiDi] Align initial browsingContext events with the spec

As discussed in https://github.com/w3c/webdriver-bidi/issues/766, and according to the HTML spec, the navigation, load and dom loaded events should not be emitted when browsing context is created.

Component: web-platform-tests → WebDriver BiDi
Product: Testing → Remote Protocol

CI Results

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

Total 4 tests and 2 subtests

Status Summary

Firefox

OK : 4
PASS : 21
FAIL : 4

Chrome

OK : 4
PASS : 21
FAIL : 4

Safari

OK : 4
ERROR: 25

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/3d290e0b98d6 [wpt PR 49327] - [WebDriver BiDi] Align initial `browsingContext` events with the spec, a=testonly https://hg.mozilla.org/integration/autoland/rev/88ee3b8aa31b [wpt PR 49327] - Update wpt metadata, a=testonly
Status: NEW → RESOLVED
Closed: 9 months ago
Resolution: --- → FIXED
Target Milestone: --- → 135 Branch
You need to log in before you can comment on or make changes to this bug.