Re: [whatwg] Fetch: number of tasks queued

2013-03-13 Thread Boris Zbarsky
On 3/13/13 10:36 AM, 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

Re: [whatwg] Fetch: number of tasks queued

2013-03-13 Thread Glenn Maynard
On Wed, Mar 13, 2013 at 9:36 AM, Anne van Kesteren ann...@annevk.nl wrote: For the test.invalid case Gecko reports both 2 and 4, Chrome/Safari only 4, and IE10 1 and then a while later 4. I think we should go with a single network task for this scenario and align with Chrome/Safari. It's

Re: [whatwg] Fetch: number of tasks queued

2013-03-13 Thread Anne van Kesteren
On Wed, Mar 13, 2013 at 2:52 PM, Boris Zbarsky bzbar...@mit.edu wrote: In gecko all fetch activity is always asynchronous, independent of URL scheme. Furthermore, the network layer can chunk up the data available callbacks however it wants to ease implementation. Nothing requires it to keep

Re: [whatwg] Fetch: number of tasks queued

2013-03-13 Thread Anne van Kesteren
On Wed, Mar 13, 2013 at 3:00 PM, Glenn Maynard gl...@zewt.org wrote: It doesn't matter how many network tasks there are, though. We can just say that if the old state is (eg.) OPENED, and we're now in DONE, that we iterate through all of the intermediary states, setting readyState and firing

Re: [whatwg] Fetch: number of tasks queued

2013-03-13 Thread Boris Zbarsky
On 3/13/13 11:14 AM, Anne van Kesteren wrote: However, if all data is typically available during state 3, developers might rely on that. Not queuing a special task that triggers state 3 for data: URLs does not preclude asynchronous loading at all. I'm not sure I follow. State 3 is LOADING.

Re: [whatwg] Fetch: number of tasks queued

2013-03-13 Thread Bjoern Hoehrmann
* 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

Re: [whatwg] Fetch: number of tasks queued

2013-03-13 Thread Glenn Maynard
On Wed, Mar 13, 2013 at 10:15 AM, Anne van Kesteren ann...@annevk.nlwrote: On Wed, Mar 13, 2013 at 3:00 PM, Glenn Maynard gl...@zewt.org wrote: It doesn't matter how many network tasks there are, though. We can just say that if the old state is (eg.) OPENED, and we're now in DONE, that we

Re: [whatwg] Fetch: number of tasks queued

2013-03-13 Thread Anne van Kesteren
On Wed, Mar 13, 2013 at 3:32 PM, Boris Zbarsky bzbar...@mit.edu wrote: What exact behavior are you proposing for the XHR implementation when it gets the callbacks described above? It sure sounds to me like you're presupposing that the some data available callbacks indicate whether there might

Re: [whatwg] Fetch: number of tasks queued

2013-03-13 Thread Boris Zbarsky
On 3/13/13 11:36 AM, Anne van Kesteren wrote: On Wed, Mar 13, 2013 at 3:32 PM, Boris Zbarsky bzbar...@mit.edu wrote: What exact behavior are you proposing for the XHR implementation when it gets the callbacks described above? It sure sounds to me like you're presupposing that the some data