- From: <bugzilla@jessica.w3.org>
- Date: Wed, 23 Feb 2011 20:24:52 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12166
Summary: 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
Product: HTML WG
Version: unspecified
Platform: Other
URL: http://www.whatwg.org/specs/web-apps/current-work/#oth
er-elements,-attributes-and-apis
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-wg-issue-tracking@w3.org,
public-html@w3.org
Specification:
http://www.whatwg.org/specs/web-apps/current-work/multipage/obsolete.html
Section:
http://www.whatwg.org/specs/web-apps/current-work/#other-elements,-attributes-and-apis
Comment:
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 breaks legacy usage. The xmp element should be regarded
as undefined in HTML5.
Posted from: 88.114.29.18
--
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 Wednesday, 23 February 2011 20:24:53 UTC