Sent by Alan Gresley on 31 March 2011 15:03
On 1/04/2011 12:31 AM, Barney Carroll wrote:
> On 31 March 2011 13:49, Markus [EMAIL-REMOVED]> wrote:
>> I could imagine a hypothetic Web application that generates class names from
>> any other information, which may start with a digit. Thus class names may
>> not even be known at coding time. In that case, escaping all digits might be
>> a valuable alternative.
>
> In that situation I would be more eager to use [class~=1] selectors —
> at least they are human readable and reproducible without any external
> methods.
>
> If you're dealing with a web app that procedurally generates
> identifiers beginning with digits and you have to support IE6-7,
> you've probably got bigger things to worry about ;)
Are you sure. Updated test case.
<http://css-class.com/test/css/selectors/identifiers-character-encoding2.htm>
IE6 and IE7 supports this as well as all other modern browsers except
for IE5.5 which sees nothing and WebKit that shows no blue border. I not
sure how older versions of Gecko, Presto or WebKit would handle the test
case.
There is good reason for all this Barney. I'm attempting to answer your
earlier email as I write this one to explain why this is so.
Thank you Philippe for making me aware of the differences in HTML4.0.1
and HTML5. I didn't realizes that a ID or NAME was not allowed to begin
with a digit in HTML4.0.1.
--
Alan http://css-class.com/
Armies Cannot Stop An Idea Whose Time Has Come. - Victor Hugo
______________________________________________________________________
css-discuss [EMAIL-REMOVED]]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
