gecko-dev/testing/web-platform/tests/priority-hints/fetch-api-request.tentative.any.js
Dominic Farolino e575760906 Bug 1466366 [wpt PR 11317] - Experimental Priority Hints support on fetch() API, a=testonly
Automatic update from web-platform-testsExperimental Priority Hints support on fetch() API

Adding support for Priority Hints on the fetch() API under an
experimental flag. This adds the notion of importance to core/fetch
code, and adds a new member to the RequestInit dictionary to communicate
developer-specified "importance" downstream.

R=kinuko@chromium.org, kouhei@chromium.org, yhirano@chromium.org, yoav@yoav.ws

Bug: 821464
Change-Id: Ib96a128d77004029e86122c07552250c697dea5f
Reviewed-on: https://chromium-review.googlesource.com/1084063
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Reviewed-by: Yoav Weiss <yoav@yoav.ws>
Commit-Queue: Dominic Farolino <domfarolino@gmail.com>
Cr-Commit-Position: refs/heads/master@{#564410}

--

wpt-commits: dae7535c0428fbf057a5c39f324d5a3f47ba64c7
wpt-pr: 11317
2018-06-25 21:49:04 +00:00

5 lines
288 B
JavaScript

test(() => {
assert_throws(new TypeError(), () => {
new Request("", {importance: 'invalid'});
}, "a new Request() must throw a TypeError if RequestInit's importance is an invalid value");
}, "new Request() throws a TypeError if any of RequestInit's members' values are invalid");