[whatwg] Augmenting HTML parser to recognize new elements

[Ryosuke Niwa]

What if content wrapped elements ignored by the parser. e.g.
<content><tr>hi</tr></content>

What should the content element include in that case?

- Ryosuke
On Jan 18, 2012 10:19 AM, "Dimitri Glazkov" <dglazkov at chromium.org> wrote:

> 'sup, Whatwg!
>
> The new HTML elements in the shadow DOM spec
> (http://dvcs.w3.org/hg/webcomponents/raw-file/tip/spec/shadow/index.html)
> and the nascent HTML templates spec (see it all explained here:
> http://dvcs.w3.org/hg/webcomponents/raw-file/tip/explainer/index.html)
> require tweaking of the HTML parsing behavior -- mostly the tree
> construction bits.
>
> A typical example would be specifying an insertion point (that's
> <content> element) as child of a <table>:
>
> <table>
>    <content>
>        <tr>
>            ...
>        </tr>
>    </content>
> </table>
>
> Both <shadow> and <template> elements have similar use cases.
>
> What would be the sane way to document such changes to the HTML parser
> behavior? A list of modifications to tree construction modes in each
> respective spec? Some "generic insertion point element" clause in the
> HTML spec? Give me ideas.
>
> Also -- what are the side effects of such a change? Surely, there's
> something I am not thinking of.
>
> :DG<
>