On 31 March 2011 15:49, Alan Gresley [EMAIL-REMOVED]> wrote:
>> 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.
Not really â€” it's a hypothetical situation, and I was making an awful
attempt at humour. I acknowledge that in practice if that situation
arose and you had to use these identifiers to style elements in IE,
the encoded characters method you've shown would work.
> Updated test case.
Is the update for the generated content tests? Removing the escape
characters will reveal the digit contentâ€¦ But I'm not sure what's
being tested for. Interestingly, Webkit's DOM inspector shows the
processed rule for span.one::before as being
No idea what that's about.
> 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.
I'm not saying there necessarily isn't a good reasonâ€¦ But I don't know
what that reason is. Thanks for the continued testing and
07594 506 381
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/