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

Re: [CSS2.1] escapes, characters and parsing

From: Gabriele Romanato <gabriele.romanato@gmail.com>
Date: Thu, 24 Mar 2011 18:19:30 +0100
Message-ID: <AANLkTinQ-FwBktOWrMyx9Ca9_LjadB78Y142wMg_Tu1L@mail.gmail.com>
To: Alan Gresley <alan@css-class.com>
Cc: CSS 3 W3C Group <www-style@w3.org>
Your tests lack of the <meta assert=""/> so it's difficult to say what is
correct or wrong here.
Generally, an escape sequence is said to remove any special meaning to the
characters that follow it.
So \* should be read as...? The point is that you're using literal tokens
here, so you should write an assert statement that says:

Description: Behavior of escape sequences with literal tokens
Assert: An escape sequence removes the special meaning of tokens.

However, an escape sequence also introduces an Unicode sequence. Since the
sequences you've provided (in the cases of \p and \*) are not valid Unicode
sequences, it's likely that some browsers ignore them and try to apply the
first thing they recognize as valid (so \p becomes p and \* becomes *).

HTH :-)


http://www.css-zibaldone.com/test/ (English)
http://www.css-zibaldone.com/articles/ (English)
http://onwebdev.blogspot.com/  (English)
Received on Thursday, 24 March 2011 17:20:02 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:38:44 UTC