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 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
Summary: The requirement on the xmp element conflicts with its old definition (which r...
Status: RESOLVED NEEDSINFO
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (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: 2011-02-23 20:24 UTC by contributor
Modified: 2011-08-04 05:34 UTC (History)
6 users (show)

See Also:

Attachments

Description contributor 2011-02-23 20:24:51 UTC 
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
Comment 1 Aryeh Gregor 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.
Comment 2 Aryeh Gregor 2011-03-04 02:47:27 UTC 
See also bug 12235, which requests making <xmp> valid.
Comment 3 Ian 'Hixie' Hickson 2011-05-05 21:58:20 UTC 
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Did Not Understand Request
Change Description: no spec change
Rationale: I don't understand this bug report. What requirements conflict with its old definition?
Comment 4 Michael[tm] Smith 2011-08-04 05:34:32 UTC 
mass-move component to LC1