W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > February 2010

[Bug 8767] <svg><font>x</font>y</svg>z is not parsed as intended. the in body insertion mode processes </font> as HTML formatting element, not as a foreign element's tag.

From: <bugzilla@wiggum.w3.org>
Date: Wed, 17 Feb 2010 23:52:46 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1NhthG-0000q1-QZ@wiggum.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8767





--- Comment #2 from Ian 'Hixie' Hickson <ian@hixie.ch>  2010-02-17 23:52:46 ---
Upon further consideration, I think the right thing to do is to add the
following as an entry in the "in foreign content" list:

An end tag, if the current node is not an element in the HTML namespace:

Run these steps:

 1. Let /node/ be the current node.

 2. Loop: If /node/ has the same tag name as the end tag token, pop elements up
to /node/ and abort. If /node/ isn't the current node, then this is a parse
error.

 3. Otherwise, let /node/ be the previous element in the stack.

 4. If /node/ is in the HTML namespace, treat the token as per the secondary
insertion mode. If, after doing so, the insertion mode is still "in foreign
content", but there is no element in scope that has a namespace other than the
HTML namespace, switch the insertion mode to the secondary insertion mode.

 5. Return to the "loop" step.


Also, change the current "An end tag" entry to be "Any other end tag".


Any opinions?


-- 
Configure bugmail: http://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 Wednesday, 17 February 2010 23:52:49 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:11 UTC