12167 2011-02-23 20:26:26 +0000 The requirement on the listing 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 2011-08-04 05:16:20 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified Other other RESOLVED WONTFIX http://www.whatwg.org/specs/web-apps/current-work/#non-conforming-features P3 normal --- 1 contributor ian ayg ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 45980 0 contributor 2011-02-23 20:26:26 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/obsolete.html Section: http://www.whatwg.org/specs/web-apps/current-work/#non-conforming-features Comment: The requirement on the listing 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 listing element should be regarded as undefined in HTML5. Posted from: 88.114.29.18 46299 1 ayg 2011-03-04 02:40:17 +0000 The HTML parser treats <listing> identically to <pre> in all respects. This implies that latest Gecko (Firefox), WebKit (Chrome/Safari), and Opera all treat it this way, since they implement the standard HTML parser. So if it ever had any such legacy meaning, apparently that meaning is no longer respected by browsers, and they've found any compatibility problems caused by that to be negligible. If the browsers are okay with this, it seems unlikely that the parsing algorithm will be changed to restore the behavior. 48112 2 ian 2011-05-05 21:56:05 +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: Rejected Change Description: no spec change Rationale: The premise of the bug seems incorrect (IE doesn't ignore the <B> in <LISTING><B>, for example, it opens a B element). I think the reporter is confusing <listing> with <xmp>. 53681 3 mike 2011-08-04 05:16:20 +0000 mass-move component to LC1