1986231 - New wpt failures in /fetch/fetch-later/basic.tentative.https.window.html

Status: NEW

(Core :: DOM: Networking, task, P3)

Description

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

Syncing wpt PR 54613 found new untriaged test failures in CI

Tests Affected

New Tests That Don't Pass

• /fetch/fetch-later/basic.tentative.https.window.html [wpt.fyi]
  • fetchLater() with same-origin (https) URL does not throw.: FAIL (Chrome: PASS, Safari: FAIL)
  • fetchLater() with https://localhost URL does not throw.: FAIL (Chrome: PASS, Safari: FAIL)
  • fetchLater() with https://127.0.0.1 URL does not throw.: FAIL (Chrome: PASS, Safari: FAIL)
  • fetchLater() with https://[::1] URL does not throw.: FAIL (Chrome: PASS, Safari: FAIL)
  • fetchLater() with https://example.com URL does not throw.: FAIL (Chrome: PASS, Safari: FAIL)
  • fetchLater() throws TypeError on file:// scheme.: FAIL (Chrome: PASS, Safari: FAIL)
  • fetchLater() throws TypeError on ftp:// scheme.: FAIL (Chrome: PASS, Safari: FAIL)
  • fetchLater() throws TypeError on ssh:// scheme.: FAIL (Chrome: PASS, Safari: FAIL)
  • fetchLater() throws TypeError on wss:// scheme.: FAIL (Chrome: PASS, Safari: FAIL)
  • fetchLater() throws TypeError on about: scheme.: FAIL (Chrome: PASS, Safari: FAIL)
  • fetchLater() throws TypeError on javascript: scheme.: FAIL (Chrome: PASS, Safari: FAIL)
  • fetchLater() throws TypeError on data: scheme.: FAIL (Chrome: PASS, Safari: FAIL)
  • fetchLater() throws TypeError on blob: scheme.: FAIL (Chrome: PASS, Safari: FAIL)

CI Results

Gecko CI (Treeherder)
GitHub PR Head

Notes

These updates will be on mozilla-central once bug 1986227 lands.

Note: this bug is for tracking fixing the issues and is not
owned by the wpt sync bot.

This bug is linked to the relevant tests by an annotation in
https://github.com/web-platform-tests/wpt-metadata. These annotations
can be edited using the wpt interop dashboard
https://jgraham.github.io/wptdash/

If this bug is split into multiple bugs, please also update the
annotations, otherwise we are unable to track which wpt issues are
already triaged. Resolving as duplicate or closing this issue should
be cause the bot to automatically update or remove the annotation.