10055 2010-06-30 09:32:17 +0000 </html> and </body> in "in foreign content" cause severe badness 2010-10-04 14:48:13 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified All All RESOLVED WORKSFORME P1 critical --- 1 hsivonen ian ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 36503 0 hsivonen 2010-06-30 09:32:17 +0000 Consider <math></html> and <dl><svg><foreignObject><div><math></body><foo> If there are allowed to transition the primary insertion mode to "after body" with no other spec changes, the tree builder ends up in "after body" with non-HTML content on the stack, which (obviously) can't be good. OTOH, if the primary insertion point stays in 'in foreign content', the loop under "An end tag, if the current node is not an element in the HTML namespace." in "in foreign content" lets </body> pop the body element off the stack (so that <foo> becomes the next sibling of body in the second example) and lets </html> pop all element off the stack, which means that a fundamental invariant of the parsing algorithm is violated. Suggested fix: Ignore "html" and "body" end tag tokens in the "in foreign content" mode. 36858 1 ian 2010-07-14 18:54:20 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Partially Accepted Change Description: no spec change Rationale: This seems to have been fixed already, though not as suggested.