[Bug 9985] New: [parser] How to parse </foo </bar>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=9985

           Summary: [parser] How to parse </foo </bar>
           Product: HTML WG
           Version: unspecified
          Platform: All
               URL: http://www.macruby.org/
        OS/Version: All
            Status: NEW
          Severity: critical
          Priority: P1
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: w3c@adambarth.com
         QAContact: public-html-bugzilla@w3.org
                CC: hsivonen@iki.fi, mike@w3.org, public-html@w3.org


WebKit received a bug report [1] about a layout problem on
http://www.macruby.org/ due to the HTML5 parsing algorithm.  (You can
visit the site in a Firefox or WebKit nightly build to see the issue.)
 The trouble boils down to this reduction:

Should say PASS:
<div>
 <div style="visibility:hidden">
   <p></p
 </div>
 PASS
</div>

Essentially, the missing ">" on the close tag of the <p> element
causes the tokenizer to consume the </div> characters as well,
resulting in the wrong DOM.  According to my tests, both the legacy
WebKit parser and the legacy Firefox parser terminate a tag token upon
encountering a "<" character.  The HTML5 spec recognizes that case as
a parse error, but has different error recovery.  (This issue is on
our "top five" list of behavioral differences likely to cause
compatibility problems.)

Is there a particular reason why we don't terminate start and end tag
tokens upon encountering a "<" character?

[1] https://bugs.webkit.org/show_bug.cgi?id=40961

-- 
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.