18107 2012-07-18 17:18:16 +0000 pre is stylistic (typografic) rather than semantic. it always has been. The use-cases should be rewritten so it becomes semantic (What is semantically wrong with using code in a p instead of a pre?) In fact, personally I do not think pre has any semantic 2012-08-23 21:26:27 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified Other other RESOLVED WONTFIX http://www.whatwg.org/specs/web-apps/current-work/#the-pre-element P3 normal --- 1 contributor dave.null eoconnor mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 70682 0 contributor 2012-07-18 17:18:16 +0000 This was was cloned from bug 16600 as part of operation convergence. Originally filed: 2012-04-02 10:33:00 +0000 ================================================================================ #0 contributor@whatwg.org 2012-04-02 10:33:34 +0000 -------------------------------------------------------------------------------- Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/grouping-content.html Multipage: http://www.whatwg.org/C#the-pre-element Complete: http://www.whatwg.org/c#the-pre-element Comment: pre is stylistic (typografic) rather than semantic. it always has been. The use-cases should be rewritten so it becomes semantic (What is semantically wrong with using code in a p instead of a pre?) In fact, personally I do not think pre has any semantic value, so why keep it other than the fact it is used so often? Simply deprecate it. Browsers can still render it so it will remain backwards compatible? Posted from: 88.244.70.57 User agent: Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20100101 Firefox/11.0 ================================================================================ 72652 1 eoconnor 2012-08-23 21:26:27 +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 change. Rationale: The <pre> element has several use cases which are difficult for Web authors to achieve by using other features. Also, the Web corpus contains a tremendous amount of <pre> usage, so we can never remove it from the platform.