- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Wed, 4 Jun 2014 09:23:29 +0200
- To: Takeshi Yoshino <tyoshino@google.com>
- 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 Wed, Jun 4, 2014 at 8:13 AM, Takeshi Yoshino <tyoshino@google.com> wrote: > On Mon, Jun 2, 2014 at 6:59 PM, Anne van Kesteren <annevk@annevk.nl> wrote: >> 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. Thanks! And my apologies for not getting that straight away. https://www.w3.org/Bugs/Public/show_bug.cgi?id=25971 > BTW, "handle a fetch" is a dead link. > https://slightlyoff.github.io/ServiceWorker/spec/service_worker/handle-a-fetch Fixed. -- http://annevankesteren.nl/
Received on Wednesday, 4 June 2014 07:24:00 UTC