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

Alan Gresley, Thu, 07 Apr 2011 04:48:03 +1000:
> On 6/04/2011 10:58 PM, Leif Halvard Silli wrote:
>> Alan Gresley, Tue, 05 Apr 2011 02:21:16 +1000:
>>> On 4/04/2011 4:18 AM, Leif Halvard Silli wrote:
>>>> timeless, Sun, 3 Apr 2011 15:51:22 +0300:
>>>>> On Sun, Feb 20, 2011 at 7:14 PM, Leif Halvard Silli wrote:

> You do mean 'neither' instead of 'whether'?

Simply put: Yes.

> This is not true. There are two definition of a newline. One is the 
> escape newline combo. The other definition of a newline ('U+0085') is 
> 'that which is outside a string'. [ snip ]

The quote which you claim to not be true, begins like this: "First, 
inside a string". So, of course it is not true outside a string.

  [...]

May be this is the most important part of your letter:

>> The Firefox bug is that it does not discern between inside and outside
>> a string. There ought to be a test case to catch that.
> 
> That's what my test cases are showing. Here are some more. These are 
> newlines outside of strings.

So it seems we actually agree, despite your claims about disagreement 
and error. You should file a bug with Mozilla. Great if you do.

> I saw that message. That is when I stared testing. Did you see this 
> message on this list?
> http://lists.w3.org/Archives/Public/www-style/2011Mar/0555.html

Yep.

>> ]]
>>   Note that this means that a "real" space after the escape sequence
>>   must be doubled. 
>> [[

> Can you point me to this spec please. I can not find those words. I 
> will need to re-test these examples.

http://www.w3.org/TR/CSS2/syndata.html#characters
-- 
leif halvard silli

Received on Thursday, 7 April 2011 00:04:19 UTC