W3C home > Mailing lists > Public > whatwg@whatwg.org > March 2013

Re: [whatwg] Fetch: number of tasks queued

From: Bjoern Hoehrmann <derhoermi@gmx.net>
Date: Wed, 13 Mar 2013 16:40:35 +0100
To: Anne van Kesteren <annevk@annevk.nl>
Message-ID: <7961k81890tcccu6gope1blnbuqmj3apln@hive.bjoern.hoehrmann.de>
Cc: WHATWG <whatwg@whatwg.org>
* Anne van Kesteren wrote:
>For the "data:text/html," case Gecko reports both 2 and 4. For
>"data:text/html,test" you get 2, 3 test, 4 test. Chrome/Safari
>dispatch 4 (without test) and then throw mentioning a synchronous
>request. Seems very much like an implementation bug. IE10 throws on
>the open() call which is a bug too. I'm leaning towards just reporting
>4 for data/about as all the data is already in.

essentially defines that a GET to data: is equivalent to a HTTP response

  HTTP/1.1 200 OK
  content-type: <type>

  <decoded data>

I see no reason why implementations should handle them differently than
how they handle such a HTTP response; that would just result in bugs,
like handling the Content-Type header in state HEADERS_RECEIVED for HTTP
and then switching to data: loads and suddenly the code stops working.
This includes of course things like not putting data in .responseText in
HEADERS_RECEIVED state when that does not happen for HTTP either.
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 
Received on Wednesday, 13 March 2013 15:41:06 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:09:20 UTC