1937661 - [wpt-sync] Sync PR 49718 - [wdspec] fix `browsingContext.navigationFailed` test

Status: RESOLVED FIXED

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

Description

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

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

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

Maksim Sadym <[e-mail]> wrote:

[wdspec] fix browsingContext.navigationFailed test

Align webdriver/tests/bidi/browsing_context/navigation_failed/navigation_failed.py:test_with_new_navigation_inside_page and test_with_new_navigation with the spec. Currently, the test are not fully aligned with the spec, as the specific event depends on the document creation step, which in order depends on the fetch status.

When WPT trickles response, it sends headers and adds timeouts before sending the body. However, this does not guarantee the new document will not be created and activated:

• Navigate, step 22.9.
• Attempt to populate the history entry's document, step 6.6.
• load a document, step 2, case "HTML MIME type".
• load an HTML document, step 1.
• create and initialize a Document object, step 9. Set during-loading navigation ID for WebDriver BiDi.

E.g. in case of Chromium, the document is created after the headers are received. This makes the discrepancy in the events have to be emitted. If the new document is created, it should be the "browsingContext.navigationAborted" event. If not, it should be "browsingContext.navigationFailed".

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=172e462de9b881c629c5031cd73b40cd340ec82f

Comment 2

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

CI Results

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

Total 1 tests and 12 subtests

Status Summary

Firefox

OK : 1
PASS : 6
FAIL : 5[Gecko-android-em-7.0-x86_64-lite-qr-opt-geckoview, Gecko-android-em-7.0-x86_64-qr-debug-geckoview, Gecko-android-em-7.0-x86_64-qr-debug-isolated-process-geckoview, Gecko-android-em-7.0-x86_64-qr-opt-geckoview] 6[Gecko-linux1804-64-qr-debug, Gecko-linux1804-64-qr-opt, Gecko-linux2204-64-wayland-debug, Gecko-linux2204-64-wayland-opt, Gecko-windows11-32-2009-qr-debug, Gecko-windows11-32-2009-qr-opt, Gecko-windows11-64-2009-qr-debug, Gecko-windows11-64-2009-qr-opt, GitHub]

Chrome

TIMEOUT: 1

Safari

OK : 1
ERROR : 12

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

• /webdriver/tests/bidi/browsing_context/navigation_failed/navigation_failed.py [wpt.fyi]
  • test_with_new_navigation: FAIL (Safari: ERROR)
  • test_with_new_navigation_inside_page: FAIL (Safari: ERROR)
  • test_close_context[tab]: FAIL (Safari: ERROR)
  • test_close_context[window]: FAIL (Safari: ERROR)
  • test_close_iframe: FAIL (Safari: ERROR)
  • test_with_beforeunload_prompt[capabilities0]: FAIL (Safari: ERROR)

Comment 3

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/cf52eb2a662a
[wpt PR 49718] - [wdspec] fix `browsingContext.navigationFailed` test, a=testonly
https://hg.mozilla.org/integration/autoland/rev/875b10b46bf5
[wpt PR 49718] - Update wpt metadata, a=testonly

Comment 4

[amarc]

https://hg.mozilla.org/mozilla-central/rev/cf52eb2a662a
https://hg.mozilla.org/mozilla-central/rev/875b10b46bf5