- From: Richard Ishida <ishida@w3.org>
- Date: Fri, 11 Jan 2013 09:12:39 +0000
- To: www International <www-international@w3.org>, W3C Style <www-style@w3.org>
I have reworked the tests that I had done so far, and summarised the results a little more carefully. You can now find the tests and summaries at the following locations: Case sensitivity in selectors (CSS/HTML5) http://www.w3.org/International/tests/html-css/selectors-case/results-selectors-case Counter style identifiers (CSS) http://www.w3.org/International/tests/html-css/counters/results-counters I need to work on something else for a while, but I'll try to come back to John Daggett's recent mail at some point with a view to expanding the tests. RI On 09/01/2013 16:00, Richard Ishida wrote: > Fwiw, I began today to put together some tests about how case is handled > in the following cases in HTML+CSS: > > - element names and selectors with different case > - attribute names and selectors... > - attribute values and ... > - class names ... > - list-style-type values in different cases > - counter-reset, counter-increment and the counter function and case > differences > > I haven't had time to fold these into our test suite and produce results > summaries, but I'll outline below my initial findings. > > See the first test at > http://www.w3.org/International/tests/html-css/generate?test=case-conversion-001 > and click on 'Next test' in the top right corner to see the others. > > Results: > > Selectors and HTML element tags match regardless of case (this is > constrained to ASCII). > > Selectors and HTML attribute names match regardless of case (this is > constrained to ASCII). > > Selectors and HTML attribute values do NOT match where case is > different. Class names using .classname syntax in the selector are a > variant of this that produces the same results except for Opera, which > matches regardless of case (though doesn't match general attribute values). > > Predefined list-style-type values produce the desired effect whether or > not an upper case value is used (this is constrained to ASCII). > > Counters are a little more complicated. Basically, if the > counter-increment property and counter function refer to a user defined > counter style using different casing, the display fails. Otherwise, case > is irrelevant. This same behaviour occurred whether the names were in > ASCII, Latin1 or Cyrillic characters. > > I tested in Firefox, Opera and Chrome on Mac and IE9 on Windows7, and > got the same results. (These are standards-mode tests.) > > Hope that helps. > RI > > > > > -- Richard Ishida Internationalization Activity Lead W3C (World Wide Web Consortium) http://www.w3.org/International/ http://rishida.net/
Received on Friday, 11 January 2013 09:13:05 UTC