On Thu, Apr 26, 2012 at 1:26 AM, Simon Pieters <simonp@...> wrote:
> On Wed, 25 Apr 2012 21:39:53 +0200, Rafael Weinstein <rafaelw@...>
>> Any other HTML tagName => HTMLBodyElement
> Isn't this one redundant with the last step?
No, this captures known HTML tagnames, so that HTML can lay claim on
the few tags that overlap with SVG. The last step just captures any
remaining tags that fell through the cracks, so they can become
>> Any other SVG tagName => SVGElement
>> Any other MathML tagName => MathElement
> What are these two, exactly? The parser currently doesn't have a list of
> SVG/MathML tag names, and the SVG WG didn't like it when it was proposed to
> use a fixed list of SVG tag names for parsing SVG in text/html, IIRC.
We don't need a specific list in the spec, but each browser would need
one, constructed from whatever elements they currently understand.
(In my dreams, we just merge SVG into the HTML namespace, and then
this step disappears.)