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

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

From: Elliott Sprehn <esprehn@gmail.com>
Date: Mon, 18 Mar 2013 09:52:12 -0700
Message-ID: <CAPJYB1gZDNOaSE4CH6zNcTc6+S9DL9PJo3uDHo6kM-AGAUKjhg@mail.gmail.com>
To: Dimitri Glazkov <dglazkov@google.com>
Cc: Dominic Cooney <dominicc@google.com>, public-webapps <public-webapps@w3.org>
On Mon, Mar 18, 2013 at 9:19 AM, Dimitri Glazkov <dglazkov@google.com>wrote:

>
> On Sun, Mar 17, 2013 at 1:46 PM, Elliott Sprehn <esprehn@gmail.com> wrote:
>
>>
>> I'd rather like it if the spec said "the component document is a document
>> that's always in standards mode and has no children" and then the contents
>> of the component were put into a DocumentFragment.
>>
>
> Should it bother us that depending on the implementation, one document
> could be shared among all component fragments or not?
>
>
That seems like an advantage to me. We can have the spec require unique
documents for now if people want, but using DocumentFragment at least lets
us decide to share in the future. Using a Document (or subclass) would
prevent us from ever making that optimization.

I think the simplicity argument is more important. Document has tons of
APIs on it that are not useful, DocumentFragment is much more focused.

- E
Received on Monday, 18 March 2013 16:53:19 GMT

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