[webkit-dev] Feature announcement: HTMLTemplateElement

Rafael Weinstein rafaelw at chromium.org
Thu Nov 29 22:05:41 PST 2012

On Thu, Nov 29, 2012 at 9:55 PM, Adam Barth <abarth at webkit.org> wrote:
> On Thu, Nov 29, 2012 at 9:23 PM, Glenn Adams <glenn at skynav.com> wrote:
>> On Thu, Nov 29, 2012 at 10:00 PM, Ryosuke Niwa <rniwa at webkit.org> wrote:
>>> On Thu, Nov 29, 2012 at 8:55 PM, Glenn Adams <glenn at skynav.com> wrote:
>>>> On Wed, Nov 28, 2012 at 1:31 PM, Rafael Weinstein <rafaelw at chromium.org>
>>>> wrote:
>>>>> Hello, WebKit!
>>>>> I plan to start landing the implementation of the HTMLTemplateElement
>>>>> (behind a compile flag).
>>>>> The spec is here:
>>>>> http://dvcs.w3.org/hg/webcomponents/raw-file/tip/spec/templates/index.html
>>>>> A recent discussion on public-webapps explored the issue and
>>>>> considered alternative approaches, but ultimately converged back to
>>>>> the semantics described in the spec above.
>>>>> The spec has support from Microsoft. Google (spec authors) and Mozilla.
>>>> How much support? Have they implemented? Deployed? What test suites are
>>>> available? What is the W3C plan for adopting this feature in the official
>>>> W3C HTML5.* spec track?

The spec is currently in the WebApps:


My assumption is that unless someone objects to it being there (rather
than HTML), it will stay.

Microsoft co-edited the spec, and made a public statement of support here:


Mozilla indicated they are looking at implementing here:


There is an test suite included in this bug which adds to the existing
html5lib test suite, which can later be merged back to w3c.

>>> We don’t typically require test suites to be available prior to
>>> implementing it in WebKit or it be in the official HTML5 specification.
>> I didnt' suggest it was. However, if test suites are not available, then I
>> would wonder about the maturity and or consensus status within the W3C
>> arena. I ask because I'm curious about the maturity/stability of this
>> feature. I also find it useful to apply a degree of caution to features that
>> are coming from WHATWG if there is no counter-commitment to move those
>> features forward in the official W3C REC track.
> Our intention is to move these this spec through the W3C REC process
> and update the implementation as the spec evolves.  As Maciej says,
> there has already been a good deal of discussion about this spec in
> the WebApps working group.  It's not clear to me whether it's more
> appropriate for the WebApps working group (where much if the other web
> components work is taking place) or the HTML working group (where HTML
> parsing is defined).  I'm sure that's something we'll need to discuss
> with the chairs and the W3C team at the appropriate time.
> Adam
> _______________________________________________
> webkit-dev mailing list
> webkit-dev at lists.webkit.org
> http://lists.webkit.org/mailman/listinfo/webkit-dev

More information about the webkit-dev mailing list