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: Ryosuke Niwa <rniwa@webkit.org>
Date: Wed, 25 Apr 2012 14:34:32 -0700
Message-ID: <CABNRm63BBeXJpGdN+2cpfTQr7rafUTQ2uj10igadX9asZBESmQ@mail.gmail.com>
To: Erik Arvidsson <arv@chromium.org>
Cc: Rafael Weinstein <rafaelw@google.com>, Yehuda Katz <wycats@gmail.com>, Webapps WG <public-webapps@w3.org>
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.

- Ryosuke

On Wed, Apr 25, 2012 at 1:51 PM, Erik Arvidsson <arv@chromium.org> wrote:

> My concern with the proposal is that it currently requires libraries
> to still do a regexp and special case frameset and html.
>
> We should imply the correct context for all tags in HTML5, not matter
> if we like them or not. I think it is important that any valid HTML
> with one top level node works and results in a firstChild that
> directly map to the input.
>
> On Wed, Apr 25, 2012 at 12:39, Rafael Weinstein <rafaelw@google.com>
> wrote:
> >> frag.innerHTML = "<frameset></frameset>a<!-- b -->"
>
> The context for this should be HTMLHtmlElement
>
> <frameset>
> <!-- b -->
>
> "a" gets dropped because it not valid as a child of <html>
>
> >> frag.innerHTML = "<html><body>foo</html>bar<tr></tr>"
>
> "root" context
>
> <html>
>  <head>
>  <body>
>     foobar
>
> >> frag.innerHTML = "<html><body>foo</html><tr></tr>"
>
> <html>
>  <head>
>  <body>
>    foo
>
> --
> erik
>
Received on Wednesday, 25 April 2012 21:35:22 GMT

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