W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2013

Re: [webcomponents]: Making <link rel="components"> produce DocumentFragments

From: Dimitri Glazkov <dglazkov@google.com>
Date: Thu, 14 Mar 2013 17:43:04 -0700
Message-ID: <CADh5Ky3rsahJRNV893_8d4X+9VSa6N6N++DJjUOH=R5yeLYENg@mail.gmail.com>
To: public-webapps <public-webapps@w3.org>
Cc: Elliott Sprehn <esprehn@gmail.com>
Here's one scenario where keeping components Documents might be a good
idea. Suppose you just built a multi-threaded parser into your renderer
engine, and you would like to hook it up to start loading multiple
components in parallel. How difficult will it be for you to do this if they
were all just DocumentFragments in the same document?

:DG<


On Mon, Mar 11, 2013 at 4:13 PM, Dimitri Glazkov <dglazkov@google.com>wrote:

> Hi folks!
>
> Just had a quick discussion with Elliott and he suggested that instead of
> building full-blown Documents, the <link rel="components"> just make
> DocumentFragments, just like <template> does.
>
> Looking at
> http://www.whatwg.org/specs/web-apps/current-work/multipage/dom.html#the-document-object and
> the bunch of APIs that will never be useful on a document without a
> browsing context, I think it's a pretty good idea. It should make also
> components more lightweight.
>
> The only problem is that now I have to figure out how to specify this
> without just flat-out stealing, err... I mean reusing, large swaths of
> HTML5 spec. But I'll take this one for the team.
>
> :DG<
>
Received on Friday, 15 March 2013 00:43:34 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:58 GMT