Re: Fetch API from Takeshi Yoshino on 2014-05-29 (public-webapps@w3.org from April to June 2014)

From: Takeshi Yoshino <tyoshino@google.com>
Date: Thu, 29 May 2014 23:25:20 +0900
To: Anne van Kesteren <annevk@annevk.nl>
Cc: public-script-coord <public-script-coord@w3.org>, Joshua Bell <jsbell@chromium.org>, Jungkee Song <jungkee.song@samsung.com>, Yehuda Katz <wycats@gmail.com>, Alex Russell <slightlyoff@google.com>, Jonas Sicking <jonas@sicking.cc>, Jake Archibald <jaffathecake@gmail.com>, Tobie Langel <tobie.langel@gmail.com>, WebApps WG <public-webapps@w3.org>
Message-ID: <CAH9hSJZt+vb9nDSVmNEQJTS+OshJME_3PWGVYf0h4txAsNTDAQ@mail.gmail.com>

http://fetch.spec.whatwg.org/#dom-request
Add steps to set client and context?

http://fetch.spec.whatwg.org/#cors-preflight-fetch-0
Add steps to set client and context?

http://fetch.spec.whatwg.org/#concept-legacy-fetch
http://fetch.spec.whatwg.org/#concept-legacy-potentially-cors-enabled-fetch
Steps to set url, client and context are missing here too. But not worth
updating this section anymore?

Termination reason is not handled intentionally (only supposed to be used
by XHR's functionalities and nothing would be introduced for Fetch API?)?

The promise is rejected with a TypeError which seems inconsistent with XHR.
Is this intentional?

Received on Thursday, 29 May 2014 14:26:08 UTC