Body reader methods do not propagate underlying errors
Reported by
ch...@anthum.com,
Mar 12 2018
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.146 Safari/537.36 Steps to reproduce the problem: 1. http://w3c-test.org/fetch/api/response/response-error-from-stream.html 2. 3. What is the expected behavior? As defined in https://github.com/w3c/web-platform-tests/blob/master/fetch/api/response/response-error-from-stream.html, CustomTestError should be reachable and accessible to Body reader Promise What went wrong? CustomTestError is not propagated and is lost/orphaned to Promise rejection. TypeError thrown instead.. Did this work before? No Does this work in other browsers? No Chrome version: 65.0.3325.146 Channel: stable OS Version: OS X 10.11.6 Flash Version: This relates to issue https://bugs.chromium.org/p/chromium/issues/detail?id=817687 Originally reported: https://github.com/whatwg/fetch/issues/676
,
Mar 12 2018
This may also apply specifically to Blink>Network>FetchAPI
,
Mar 13 2018
Thanks for filing the issue! Checked the issue on reported chrome version 65.0.3325.146 using Mac 10.13.1 with the below mentioned steps. 1. Launched Chrome 2. Navigated to http://w3c-test.org/fetch/api/response/response-error-from-stream.html 3. On Checking the check box for 2 pass and 10 fail gave us the filtered results. 4. using the code given in https://github.com/w3c/web-platform-tests/blob/master/fetch/api/response/response-error-from-stream.html created an html file and opened in a new tab. It resulted in a blank page. @Reporter: As we are not clear about the expected and actual behaviour, it would be highly helpful if provided with screencast/screenshot explaining the issue. Requesting "ricea" from Issue 817687 for further inputs on this.
,
Mar 13 2018
#1 Is this the same problem as issue 777487 ? #3 The expected behaviour is that all 12 tests pass. https://github.com/w3c/web-platform-tests/blob/master/fetch/api/response/response-error-from-stream.html won't work without the proper server configuration; since w3c-test.org provides that configuration, it's easiest to use the http://w3c-test.org/fetch/api/response/response-error-from-stream.html URL to reproduce. Lowering priority to 3 as it has been broken for a long time. |
|||
►
Sign in to add a comment |
|||
Comment 1 by krajshree@chromium.org
, Mar 12 2018Labels: Needs-Triage-M65