W3C home > Mailing lists > Public > whatwg@whatwg.org > June 2014

Re: [whatwg] Fetch API: asHTML

From: Adam Barth <w3c@adambarth.com>
Date: Sat, 21 Jun 2014 21:10:43 -0700
Message-ID: <CAJE5ia-4rCX4JknFRJ9-RRdLiJLFc6Rdm6R2Cbn8zORZoFMrTA@mail.gmail.com>
To: Joshua Peek <josh@joshpeek.com>
Cc: WHATWG <whatwg@whatwg.org>
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.


On Fri, Jun 20, 2014 at 2:39 PM, Joshua Peek <josh@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!
Received on Sunday, 22 June 2014 04:11:42 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:21 UTC