10621 2010-09-13 07:10:36 +0000 Processing EOF InForeignContent mode can cause an infinite loop if we don't switch the insertion model to the secondary insertion mode. Suppose the input is <svg><title>. Now, we won't pop anything off the stack of open elements. The insertion mode wil 2010-10-22 10:28:35 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified Other other VERIFIED DUPLICATE 10588 http://www.whatwg.org/specs/web-apps/current-work/#scriptForeignEndTag P3 normal --- 1 contributor ian eric hsivonen mike Ms2ger public-html-admin public-html-wg-issue-tracking w3c public-html-bugzilla oldest_to_newest 38954 0 contributor 2010-09-13 07:10:36 +0000 Section: http://www.whatwg.org/specs/web-apps/current-work/#scriptForeignEndTag Comment: Processing EOF InForeignContent mode can cause an infinite loop if we don't switch the insertion model to the secondary insertion mode. Suppose the input is <svg><title>. Now, we won't pop anything off the stack of open elements. The insertion mode will still be in foreign content, but we'll still have an element in scope outside the HTML namespace (namely the svg:title element). Reprocessing the token, then, leads to an infinite loop. Posted from: 67.169.42.39 by w3c@adambarth.com 38959 1 hsivonen 2010-09-13 09:34:05 +0000 *** This bug has been marked as a duplicate of bug 10588 ***