W3C home > Mailing lists > Public > www-style@w3.org > April 2011

Re: [CSS21] Escaping characters (comment, editorial)

From: Alan Gresley <alan@css-class.com>
Date: Thu, 07 Apr 2011 06:23:47 +1000
Message-ID: <4D9CCBD3.2080903@css-class.com>
To: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
CC: timeless <timeless@gmail.com>, www-style@w3.org
On 7/04/2011 4:48 AM, Alan Gresley wrote:

> Take this example.
>
>
> /* escape below */
> /
>
> /* newline above */


Correction. That should had been this.


/* escape below */
\

/* newline above */


Firefox 3.6.16 treats this as if the escape was within a string.


http://css-class.com/test/css21testsuite/newline-008.xht


This is a bug.


> How can both the escape ending one line and a newline at the beginning
> of a newline cancels the meaning of the literal newline 'U+0085' that is
> outside of a string?


What I mean by this is shown below.


   /*
  /  *
/   *
--- * -- U+0085
    *
   *
*

The escape and newline within a string is inside but the U+0085 is 
parsed as if it was outside this string.


-- 
Alan http://css-class.com/

Armies Cannot Stop An Idea Whose Time Has Come. - Victor Hugo
Received on Wednesday, 6 April 2011 20:24:16 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:39 GMT