I haven't been following the fetch API in detail. Is there some collective understanding of what abstraction layer fetch represents? For example, I could imagine that we might not want to add a dependency from the fetch to the HTML parser because fetch is a lower layer of the system.
Adam On Fri, Jun 20, 2014 at 2:39 PM, Joshua Peek <j...@joshpeek.com> wrote: > Hey Anne, love the direction of the Fetch API. > > I'm curious what you think of an asHTML extension to the FetchBodyStream? > > Parsing fragment HTML from XHRs is pretty typical. It could potential > return a DocumentFragment or if it used some streaming HTML parser, it > could emit the top level nodes as they were being parsed. > > Any reasons why its a terrible idea? Or just something thats a little > to complex to tackle in the early states of Fetch? > > Thanks!