This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 10621 - 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
Summary: Processing EOF InForeignContent mode can cause an infinite loop if we don't s...
Status: VERIFIED DUPLICATE of bug 10588
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-13 07:10 UTC by contributor
Modified: 2010-10-22 10:28 UTC (History)
7 users (show)

See Also:

Attachments

Description contributor 2010-09-13 07:10:36 UTC 
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
Comment 1 Henri Sivonen 2010-09-13 09:34:05 UTC 

*** This bug has been marked as a duplicate of bug 10588 ***