Re: [whatwg] Undefined spec about removing node in a range.

2014-08-12 Thread Anne van Kesteren
On Mon, Aug 11, 2014 at 10:16 AM, Yoichi Osato yoic...@google.com wrote: I guess the case 2 and 3 should be: 2. For each range whose start node is a inclusive descendant of node, set its start to (parent, index). 3. For each range whose end node is a inclusive descendant of node, set its end

[whatwg] [Fetch] ambiguity problem?

2014-08-12 Thread Brian Kardell
Not wanting to start a giant bikeshed here but if you have a look at Jake's Service Worker Examples as an early use of fetch and streams, it seems clear that many developers would be surprised by behavior of not being about to refer back to the response body. I'd like to suggest that this is less

Re: [whatwg] [Fetch] ambiguity problem?

2014-08-12 Thread Brian Kardell
On Aug 12, 2014 9:07 AM, Brian Kardell bkard...@gmail.com wrote: Not wanting to start a giant bikeshed here but if you have a look at Jake's Service Worker Examples as an early use of fetch and streams, it seems clear that many developers would be surprised by behavior of not being about to

Re: [whatwg] [Fetch] ambiguity problem?

2014-08-12 Thread Anne van Kesteren
On Tue, Aug 12, 2014 at 3:07 PM, Brian Kardell bkard...@gmail.com wrote: Not wanting to start a giant bikeshed here but if you have a look at Jake's Service Worker Examples as an early use of fetch and streams, it seems clear that many developers would be surprised by behavior of not being

Re: [whatwg] [Fetch] ambiguity problem?

2014-08-12 Thread Brian Kardell
On Aug 12, 2014 9:13 AM, Anne van Kesteren ann...@annevk.nl wrote: On Tue, Aug 12, 2014 at 3:07 PM, Brian Kardell bkard...@gmail.com wrote: Not wanting to start a giant bikeshed here but if you have a look at Jake's Service Worker Examples as an early use of fetch and streams, it seems

Re: [whatwg] [Fetch] ambiguity problem?

2014-08-12 Thread Anne van Kesteren
On Tue, Aug 12, 2014 at 4:40 PM, Brian Kardell bkard...@gmail.com wrote: In what way? . response is a completely read DOMString or Object or whatever, not a Stream? In that you cannot get back to the original response. You can only get it in one chosen variant. -- http://annevankesteren.nl/

Re: [whatwg] [Fetch] ambiguity problem?

2014-08-12 Thread Brian Kardell
On Aug 12, 2014 10:45 AM, Anne van Kesteren ann...@annevk.nl wrote: On Tue, Aug 12, 2014 at 4:40 PM, Brian Kardell bkard...@gmail.com wrote: In what way? . response is a completely read DOMString or Object or whatever, not a Stream? In that you cannot get back to the original response. You

Re: [whatwg] [Fetch] ambiguity problem?

2014-08-12 Thread Anne van Kesteren
On Tue, Aug 12, 2014 at 7:22 PM, Brian Kardell bkard...@gmail.com wrote: If I do console. log(o.responseText); console. log(o.responseText); The second one will be what? The response text or nada? Isn't the later more analogous to what we're taking about here when it's a stream? It feels

Re: [whatwg] [Fetch] ambiguity problem?

2014-08-12 Thread Domenic Denicola
From: whatwg whatwg-boun...@lists.whatwg.org on behalf of Brian Kardell bkard...@gmail.com console. log(o.responseText); console. log(o.responseText); This is why I've been advocating for asJSON() and friends to be verbs, not nouns, i.e. readAsJSON(). Showing how you take an action makes you

Re: [whatwg] [Fetch] ambiguity problem?

2014-08-12 Thread Brian Kardell
On Aug 12, 2014 1:38 PM, Domenic Denicola dome...@domenicdenicola.com wrote: From: whatwg whatwg-boun...@lists.whatwg.org on behalf of Brian Kardell bkard...@gmail.com console. log(o.responseText); console. log(o.responseText); This is why I've been advocating for asJSON() and friends to