W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > July 2011

[Bug 13293] Undefined behavior for EOF in foreign content mode

From: <bugzilla@jessica.w3.org>
Date: Tue, 19 Jul 2011 23:50:36 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1QjK3g-0008IA-Ak@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13293

Aryeh Gregor <Simetrical+w3cbug@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |Simetrical+w3cbug@gmail.com

--- Comment #1 from Aryeh Gregor <Simetrical+w3cbug@gmail.com> 2011-07-19 23:50:35 UTC ---
I'm not so familiar with the HTML parsing algorithm, but as I read it, an EOF
token is never emitted in foreign content.  Specifically, at

http://www.whatwg.org/specs/web-apps/current-work/multipage/tokenization.html#tree-construction

it says

"As each token is emitted from the tokenizer, the user agent must follow the
appropriate steps from the following list:"

The step "If the token is an end-of-file token" says

"Process the token according to the rules given in the section corresponding to
the current insertion mode in HTML content."

So it looks to me like you first do tokenization, then decide the insertion
mode (foreign vs. HTML) based on the current token, and EOF is always processed
in HTML insertion mode.  If some elements are still open, this will be a parse
error, per the rules of the HTML insertion mode.  Are you reading it
differently?

-- 
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 Tuesday, 19 July 2011 23:50:37 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:13 UTC