New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 766975 link

Starred by 2 users

Issue metadata

Status: Fixed
OoO until Feb 4th
Closed: Sep 2017
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Sign in to add a comment

Fetch: Stop checking Request.integrity's value in no-cors mode

Project Member Reported by, Sep 20 2017

Issue description

We need to update our Fetch implementation to a recent spec change that removed the "If request ’s integrity metadata is not the empty string, then throw a TypeError" bit from Request's constructor algorithm.

Upstream bug report:
Upstream spec change:
WPT change:
Project Member

Comment 1 by, Sep 21 2017

The following revision refers to this bug:

commit 7d97c3a8550e35ce8af356fa6e3e8a0553a61140
Author: Raphael Kubo da Costa <>
Date: Thu Sep 21 10:44:54 2017

Fetch: Do not check |integrity| in no-cors mode when constructing a Request

Adapt to, which removed the check
for |integrity|'s value when constructing a Request in no-cors mode.

Per "the issue is that it's
pretty common to do <script integrity="hash"> in your document. This creates
a no-cors request by default. If their service worker script passes through
with fetch(evt.request) then they will get a TypeError."

Note that the external tests added in
are still flaky.

Bug:  766975 ,  766983 
Change-Id: I1a787ee39ed94db49ba18f8675edc7dc3019ed26
Commit-Queue: Raphael Kubo da Costa (rakuco) <>
Reviewed-by: Tsuyoshi Horo <>
Reviewed-by: Yutaka Hirano <>
Cr-Commit-Position: refs/heads/master@{#503412}

Labels: M-63
Status: Fixed (was: Started)
Done. Note that  bug 766983  reports some of the WPT tests upstream seem to be flaky.

Sign in to add a comment