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

[Bug 10080] New: "in body" insertion mode, "any other end tag", step 2.2 seems wrong.

From: <bugzilla@jessica.w3.org>
Date: Sun, 04 Jul 2010 20:10:43 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-10080-2486@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10080

           Summary: "in body" insertion mode, "any other end tag", step
                    2.2 seems wrong.
           Product: HTML WG
           Version: unspecified
          Platform: Other
               URL: http://www.whatwg.org/specs/web-apps/current-work/#fos
                    ter-parenting
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P3
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: eric@webkit.org
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html@w3.org, w3c@adambarth.com,
                    eric@webkit.org
        Depends on: 10063


"in body" insertion mode, "any other end tag", step 2.2 seems wrong:

2. If node has the same tag name as the token, then:

2.1 Generate implied end tags.

2.2 If the tag name of the end tag token does not match the tag name of the
current node, this is a parse error.

2.3 Pop all the nodes from the current node up to node, including node, then
stop these steps.


2.2. should instruct implementors to abort the steps after the parse error,
since reaching 2.3, having already popped the node in 2.1 will fail?

-- 
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 Sunday, 4 July 2010 20:10:45 UTC

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