W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2014

Re: Fetch API

From: Takeshi Yoshino <tyoshino@google.com>
Date: Wed, 4 Jun 2014 15:13:15 +0900
Message-ID: <CAH9hSJY8XVbaqLaGcs0vCLUn_54FoYWtOM8w0Acr7wWa2DQE7g@mail.gmail.com>
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>
On Mon, Jun 2, 2014 at 6:59 PM, Anne van Kesteren <annevk@annevk.nl> wrote:

> On Thu, May 29, 2014 at 4:25 PM, Takeshi Yoshino <tyoshino@google.com>
> wrote:
> > http://fetch.spec.whatwg.org/#dom-request
> > Add steps to set client and context?
> That happens as part of the "restricted copy". However, that might
> still change around a bit.

Ah, ok.

> > http://fetch.spec.whatwg.org/#cors-preflight-fetch-0
> > Add steps to set client and context?
> That's an internal algorithm never directly used. You can only get
> there from http://fetch.spec.whatwg.org/#concept-fetch and that can
> only be reached through an API such as fetch().

Right. But preflight's client and context are not initialized before
invoking HTTP fetch (http://fetch.spec.whatwg.org/#concept-http-fetch).
client is referred in HTTP fetch.

BTW, "handle a fetch" is a dead link.

> > The promise is rejected with a TypeError which seems inconsistent with
> XHR.
>  > Is this intentional?
> Yes. I wanted to stick to JavaScript exceptions. However, I suspect at
> some point once we have FormData integration and such there might be
> quite a bit of dependencies on DOM in general, so maybe that is moot.

Got it. Thanks.
Received on Wednesday, 4 June 2014 06:14:03 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:24 UTC