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

[Bug 10055] New: </html> and </body> in "in foreign content" cause severe badness

From: <bugzilla@jessica.w3.org>
Date: Wed, 30 Jun 2010 09:32:17 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-10055-2486@http.www.w3.org/Bugs/Public/>

           Summary: </html> and </body> in "in foreign content" cause
                    severe badness
           Product: HTML WG
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: critical
          Priority: P1
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: hsivonen@iki.fi
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html@w3.org


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.

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, 30 June 2010 09:32:19 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:30:51 UTC