9582 2010-04-22 14:45:43 +0000 Steps for handling end tags in the "in foreign" mode get stuck in an infinite loop 2010-10-04 13:58:45 +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 35218 0 hsivonen 2010-04-22 14:45:43 +0000 In the text added in rev 4803, the step "Set node to the previous entry in the stack of open elements." is not a sufficient advancement to make the loop terminate when node becomes a node that has already been popped by the secondary insertion mode in the previous iteration. To make things advance, it is necessary to jump right back to the "Loop:" label in that case. Or more importantly, you might want to abort processing the end tag if insertion mode is no longer "in foreign". 35756 1 hsivonen 2010-05-19 07:15:03 +0000 Adjusting importance per discussion with Hixie. 35883 2 hsivonen 2010-05-31 11:00:52 +0000 http://hg.mozilla.org/mozilla-central/file/62c09fac599a/parser/html/javasrc/TreeBuilder.java#l3109 shows how I improvised around this bug. 36502 3 hsivonen 2010-06-30 08:57:59 +0000 http://hg.mozilla.org/projects/htmlparser/rev/b08b9993cd5d#l1.64 is the fix for this bug. 36820 4 ian 2010-07-14 00:38:54 +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: If I understand this correctly, it is fixed by the fix to bug 9580.