W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2012

Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Wed, 25 Apr 2012 15:18:56 -0700
Message-ID: <CAAWBYDD4ZaGbaK4F+b94z5V6wHouEHh1Rr_ZxeiMOpSPZiQdVA@mail.gmail.com>
To: Ryosuke Niwa <rniwa@webkit.org>
Cc: Erik Arvidsson <arv@chromium.org>, Rafael Weinstein <rafaelw@google.com>, Yehuda Katz <wycats@gmail.com>, Webapps WG <public-webapps@w3.org>
On Wed, Apr 25, 2012 at 2:34 PM, Ryosuke Niwa <rniwa@webkit.org> wrote:
> I agree. Changing the context element based on the first element is strange
> and counter-intutitive and doesn't buy us anything.
>
> For example, enforcing the "in table" insertion mode when we encounter td as
> the first element doesn't guarantee into where this fragment is inserted. In
> fact, it can be inserted as an immediate child of a shadow root for the
> component model.

If you have a fragment that starts with a "<td>", you'd better be
planning on eventually putting it as the child of a <tr>.  (Or as the
shadow children of a Component that is acting like a <tr>.)

If you want to do something else... um, why?  What possible use-case
might there be for parsing a string starting with "<td>" aside from
later putting it inside a <tr>?

~TJ
Received on Wednesday, 25 April 2012 22:19:46 GMT

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