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

Re: [webcomponents] Making the shadow root an Element

From: Dimitri Glazkov <dglazkov@google.com>
Date: Mon, 18 Feb 2013 13:12:58 -0800
Message-ID: <CADh5Ky19iiGaiRrJDvDDtVcpwmyDHHg06qb286L50m=9JggX-Q@mail.gmail.com>
To: Anne van Kesteren <annevk@annevk.nl>
Cc: Jonas Sicking <jonas@sicking.cc>, "Tab Atkins Jr." <jackalmage@gmail.com>, public-webapps <public-webapps@w3.org>
On Mon, Feb 18, 2013 at 1:01 PM, Anne van Kesteren <annevk@annevk.nl> wrote:
> On Mon, Feb 18, 2013 at 8:57 PM, Dimitri Glazkov <dglazkov@google.com> wrote:
>> Still unclear. Are you saying this: if we have API members on
>> ShadowRoot that aren't on DocumentFragment, then ShadowRoot should not
>> be a DocumentFragment?
>
> No. all I'm saying that "we" made a conscious choice not to have
> innerHTML on DocumentFragment and that therefore we should not
> introduce it on ShadowRoot either (until we either revisit the
> DocumentFragment decision or someone shows that decision is not
> applicable to ShadowRoot somehow).

Ah, got it. Well... The innerHTML is necessary for ShadowRoot. It's
not a matter of API taste or consistency. If you look at any shadow
DOM code today (however experimental), you'll see most of it using
innerHTML to populate the shadow tree.

Perhaps you had an good analogous API in mind?

:DG<
Received on Monday, 18 February 2013 21:13:26 GMT

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