9581 2010-04-22 14:33:22 +0000 Steps for handling end tags in the "in foreign" mode may compare the name of an already-popped node 2010-10-04 14:56:54 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified PC Linux RESOLVED FIXED http://html5.org/tools/web-apps-tracker?from=4802&to=4803 P1 critical --- 1 hsivonen ian ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 35217 0 hsivonen 2010-04-22 14:33:22 +0000 In the text added in rev 4803, the condition "If node has the same tag name as the token" is checked even if node has already been popped by the handling in the secondary insertion mode in the previous iteration. 35755 1 hsivonen 2010-05-19 07:14:45 +0000 Adjusting importance per discussion with Hixie. 35884 2 hsivonen 2010-05-31 11:01:04 +0000 http://hg.mozilla.org/mozilla-central/file/62c09fac599a/parser/html/javasrc/TreeBuilder.java#l3109 shows how I improvised around this bug. 36500 3 hsivonen 2010-06-30 08:56:53 +0000 the left-hand part of the |if| condition on line http://hg.mozilla.org/projects/htmlparser/rev/b08b9993cd5d#l1.57 fixes this bug 36504 4 hsivonen 2010-06-30 12:10:15 +0000 From #whatwg 14:32 < jgraham> hsivonen: It seems to work OK with the html5lib test cases if you break when node is no longer in the stack of open elements after step 5 36819 5 ian 2010-07-14 00:38:18 +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: see diff given below Rationale: This is fixed by the fix to bug 9580.