Closed Bug 1863313 Opened 2 years ago Closed 2 years ago

[wpt-sync] Sync PR 42969 - [wdspec] network intercept: navigate instead of fetch

Categories

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

task

Tracking

(firefox122 fixed)

RESOLVED FIXED
122 Branch
Tracking Status
firefox122 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Thiago Perrotta <tperrotta@chromium.org> wrote:

[wdspec] network intercept: navigate instead of fetch

Use navigation with an expected timeout instead of fetch with an expected exception.

From a test implementation perspective this is a no-op as, when the network interception triggers, the navigation is expected to not complete (and thus timeout).

Component: web-platform-tests → WebDriver BiDi
Product: Testing → Remote Protocol
PR 42969 applied with additional changes from upstream: ae3989ed3129b72ae685de5e86e841bb79d598a8
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]

CI Results

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

Total 1 tests and 3 subtests

Status Summary

Firefox

OK : 1
PASS : 3

Chrome

TIMEOUT: 1

Safari

OK : 1
ERROR : 3

Links

GitHub PR Head
GitHub PR Base

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/418164985235 [wpt PR 42969] - [wdspec] network intercept: navigate instead of fetch, a=testonly
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/c5e9957cebc4 [wpt PR 42969] - [wdspec] network intercept: navigate instead of fetch, a=testonly
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 122 Branch
You need to log in before you can comment on or make changes to this bug.