W3C home > Mailing lists > Public > whatwg@whatwg.org > September 2009

[whatwg] Initial carriage return in <pre> and <textarea>

From: Henri Sivonen <hsivonen@iki.fi>
Date: Fri, 11 Sep 2009 14:30:33 +0300
Message-ID: <372778E2-4109-40B2-84A8-FB3CCB166784@iki.fi>

On Sep 11, 2009, at 11:39, Simon Pieters wrote:

> On Fri, 11 Sep 2009 10:12:59 +0200, Henri Sivonen <hsivonen at iki.fi>  
> wrote:
>
>> On Sep 10, 2009, at 23:40, ?istein E. Andersen wrote:
>>
>>> ? 9.1.2.5 "Restrictions on content models" mentions that an  
>>> initial line feed (\n) character inside <pre> and <textarea> will  
>>> be removed.  Should it not cover carriage return (\r) and \r\n as  
>>> well?
>>
>>
>> If you put \r or \r\n in the source, you are expressing a \n. If  
>> you want to express a \r, you need to escape it, and then the tree  
>> builder doesn't zap it.
>
> &#xD; also ends up being \n in HTML, no?

Yes. Escaping \n doesn't make the tree builder preserve it.

-- 
Henri Sivonen
hsivonen at iki.fi
http://hsivonen.iki.fi/
Received on Friday, 11 September 2009 04:30:33 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:52 UTC