13653 2011-08-04 01:41:09 +0000 For PRE element "In the HTML syntax, a leading newline character immediately following the pre element start tag is stripped." The same should hold true for code also, when use inside a pre (<pre><code> my code </code></pre>) If not in the spec, could you 2011-08-05 14:50:28 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified Other other RESOLVED WONTFIX http://www.whatwg.org/specs/web-apps/current-work/#top P3 normal --- 1 contributor ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 52293 0 contributor 2011-08-04 01:41:09 +0000 Specification: http://dev.w3.org/html5/spec/Overview.html Multipage: http://www.whatwg.org/C#top Complete: http://www.whatwg.org/c#top Comment: For PRE element "In the HTML syntax, a leading newline character immediately following the pre element start tag is stripped." The same should hold true for code also, when use inside a pre (<pre><code> my code </code></pre>) If not in the spec, could you add it? Reason: same as for <pre>: code readibility Posted from: 89.157.69.5 User agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.30 (KHTML, like Gecko) Chrome/12.0.742.122 Safari/534.30 52879 1 mike 2011-08-04 05:05:03 +0000 mass-moved component to LC1 54239 2 zcorpan 2011-08-05 14:50:28 +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 line stripping is done because it's what browsers did prior to specifying the parsing rules. Browsers don't do it for <code>. Changing this would affect existing sites that use <pre><code>\n and expect a leading newline.