[Bug 10621] New: 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

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

           Summary: 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
           Product: HTML WG
           Version: unspecified
          Platform: Other
               URL: http://www.whatwg.org/specs/web-apps/current-work/#scr
                    iptForeignEndTag
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P3
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: contributor@whatwg.org
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html@w3.org, w3c@adambarth.com


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

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

Received on Monday, 13 September 2010 07:10:38 UTC