W3C home > Mailing lists > Public > public-webapps-bugzilla@w3.org > February 2012

[Bug 14694] innerHTML in DocumentFragment

From: <bugzilla@jessica.w3.org>
Date: Tue, 28 Feb 2012 21:41:14 +0000
To: public-webapps-bugzilla@w3.org
Message-Id: <E1S2UnK-0002XH-QQ@jessica.w3.org>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=14694

Dimitri Glazkov <dglazkov@chromium.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Blocks|                            |15658

--- Comment #4 from Dimitri Glazkov <dglazkov@chromium.org> 2012-02-28 21:41:13 UTC ---
For those interested, I am working on this as part of the HTML templates spec.

See a slightly out-of-date spec here:
http://dvcs.w3.org/hg/webcomponents/raw-file/tip/spec/templates/index.html#parsing

It's out of date because I then went to play with WebKit's HTML parser to make
it do this, purely to learn more about parsing:
https://bugs.webkit.org/show_bug.cgi?id=78734, which revealed a few more places
that still need spec work.

Since that templates are defined as a vehicle to build document fragments
declaratively, the DWIM insertion mode (called "template contents" mode in HTML
Templates draft) effectively describes the behavior of
DocumentFragment.prototype.set.

However for templates, there's also another degree of freedom of the context in
which a <template> tag can appear.

I am ok with keeping both together or separate. Whatever makes things move
faster. I have both time, energy, and now a bit of expertise to write the
modifications. Just need a consensus on the path :)

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Tuesday, 28 February 2012 21:41:17 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 28 February 2012 21:41:17 GMT