12166 2011-02-23 20:24:51 +0000 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 2011-08-04 05:34:32 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified Other other RESOLVED NEEDSINFO http://www.whatwg.org/specs/web-apps/current-work/#other-elements,-attributes-and-apis P3 normal --- 1 contributor ian ayg ian julian.reschke mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 45979 0 contributor 2011-02-23 20:24:51 +0000 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 46296 1 ayg 2011-03-04 02:36:57 +0000 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. 46301 2 ayg 2011-03-04 02:47:27 +0000 See also bug 12235, which requests making <xmp> valid. 48113 3 ian 2011-05-05 21:58:20 +0000 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? 53925 4 mike 2011-08-04 05:34:32 +0000 mass-move component to LC1