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

[Bug 12166] The requirement on the xmp element conflicts with its old definition (which requires a special parsing mode where no markup except the element's end tag is recognized) and usage. It is better to avoid requiring any support than to require support that bre

From: <bugzilla@jessica.w3.org>
Date: Fri, 04 Mar 2011 02:36:58 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1PvKt0-0005N0-0z@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12166

--- Comment #1 from Aryeh Gregor <Simetrical+w3cbug@gmail.com> 2011-03-04 02:36:57 UTC ---
xmp is treated differently by the HTML parser, as its conventional meaning
requires.  See the part here labeled 'A start tag whose tag name is "xmp"':

http://www.whatwg.org/specs/web-apps/current-work/multipage/tokenization.html#parsing-main-inbody

A note to authors of this fact might be worthwhile, so that they don't have to
look into the parser section.

-- 
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 Friday, 4 March 2011 02:36:59 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 4 March 2011 02:37:02 GMT