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: Fri, 11 May 2012 12:12:47 +0200
Message-ID: <CAAWBYDAV+-grkDLg_JAzUMsq26HeFi0XNtNj1bvGeTniPOWjsA@mail.gmail.com>
To: Ryosuke Niwa <rniwa@webkit.org>
Cc: Henri Sivonen <hsivonen@iki.fi>, Rafael Weinstein <rafaelw@google.com>, Webapps WG <public-webapps@w3.org>, Yehuda Katz <wycats@gmail.com>
On Fri, May 11, 2012 at 11:59 AM, Ryosuke Niwa <rniwa@webkit.org> wrote:
> On Fri, May 11, 2012 at 1:55 AM, Henri Sivonen <hsivonen@iki.fi> wrote:
>> I still think that having to create a DocumentFragment first and then
>> set innerHTML on it is inconvenient and we should have a method on
>> document that takes a string to parse and returns the resulting
>> DocumentFragment, e.g. document.parse(string) to keep it short.
>
> Yes! Can we re-use createDocumentFragment and add an optional argument
> instead though?

That seems unacceptably verbose.  :/  I doubt people will be happy
trading in their single-character $ for the 22-character
createDocumentFragment.  document.parse is 14 characters, which is
less than ideal, but still much better.

~TJ
Received on Friday, 11 May 2012 10:13:36 GMT

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