Re: [fetch-tests] Adding an error test where the error happens after the fetch promise resolution (#3951) from Yutaka Hirano on 2016-10-17 (public-web-platform-tests-notifications@w3.org from October 2016)

From: Yutaka Hirano <web-platform-tests-notifications@w3.org>
Date: Mon, 17 Oct 2016 12:33:01 GMT
To: public-web-platform-tests-notifications@w3.org
Message-Id: <<web-platform-tests_issue_3951_1476707581010@w3.org>>

Sorry for the delayed response.

The test fails on Chrome from two reasons:

1. Chrome applies mime sniffing. That means Chrome buffers first some bytes to determine/verify the mime type and then dispatch a responseReceived message. 10 bytes is small enough to be buffered.
2. Chrome errors a stream by DOMException(NetworkError) not by TypeError.

I resolved the former issue recently: https://codereview.chromium.org/2323623002/. After a few months the stable release will include the change. I don't know why we are using DOMException instead of TypeError. I will fix it shortly.

Thanks,



View on GitHub: https://github.com/w3c/web-platform-tests/pull/3951#issuecomment-254194416

Received on Monday, 17 October 2016 12:33:09 UTC