14833 2011-11-15 14:02:37 +0000 "If current node is a pre, textarea, or listing element, append a U+000A LINE FEED (LF) character." - no browser does this and when we tried it caused site-compat problems. It should either be removed or changed to only emit a extra LF if the element's fi 2013-03-27 13:09:33 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#serializing-html-fragments P3 normal Unsorted 1 contributor ian ian mike roan.kattouw zcorpan contributor oldest_to_newest 60045 0 contributor 2011-11-15 14:02:37 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/ Multipage: http://www.whatwg.org/C#serializing-html-fragments Complete: http://www.whatwg.org/c#serializing-html-fragments Comment: "If current node is a pre, textarea, or listing element, append a U+000A LINE FEED (LF) character." - no browser does this and when we tried it caused site-compat problems. It should either be removed or changed to only emit a extra LF if the element's first child is a text node starting with a LF. Posted from: 2001:4c28:a030:30:219:99ff:fe0e:5501 User agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0a1) Gecko/20111009 Firefox/10.0a1 61160 1 ian 2011-12-07 23:22:37 +0000 Well we definitely need something here, otherwise we'll get dataloss if there's a leading LF. But I can change it to be more conservative in when they are added, sure. 63381 2 contributor 2012-01-31 00:39:18 +0000 Checked in as WHATWG revision r6940. Check-in comment: Make HTML serialisation more conservative near <pre>. http://html5.org/tools/web-apps-tracker?from=6939&to=6940 82680 3 roan.kattouw 2013-02-07 03:47:33 +0000 (In reply to comment #1) > Well we definitely need something here, otherwise we'll get dataloss if > there's a leading LF. But I can change it to be more conservative in when > they are added, sure. Thanks! The data loss issue has been bothering me for a while, and I've had to hack around it in some of my code. The console session in http://pastebin.com/64Jjs4NH demonstrates the insanity I'm dealing with. Sadly, comment 0 is right that no browser does this. Both Firefox and Chrome completely ignore this rule, causing data loss when parsing and reserializing <pre>s and <textarea>s whose contents start with a newline. I hope browsers will actually fix this behavior in the future. I guess I'll have to tweak my hack such that it will work both for broken browsers and fixed ones. 82682 4 roan.kattouw 2013-02-07 04:32:10 +0000 (In reply to comment #3) > I hope browsers will actually fix this behavior in the future. Filed https://bugzilla.mozilla.org/show_bug.cgi?id=838954 against Firefox and https://code.google.com/p/chromium/issues/detail?id=174829 against Chrome. 85055 5 zcorpan 2013-03-27 13:09:33 +0000 (In reply to comment #3) > Sadly, comment 0 is right that no browser does this. Opera has implemented and shipped the spec change here.