- From: <bugzilla@jessica.w3.org>
- Date: Wed, 12 Feb 2014 04:50:14 +0000
- To: public-i18n-core@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16970 --- Comment #9 from John Daggett <jdaggett@mozilla.com> --- Yes, I understand the limitations of ASCII case-insensitivity!! But my original point in comment 5 was that using a *new* caseless matching algorithm in a way that's inconsistent with other legacy usage that instead uses case-sensitive or ASCII case-insensitive comparisons is both confusing and unnecessary. In an ideal world, the choices would be either case-sensitive or some form of Unicode case-insensitive matching but that's not what exists today. It doesn't make much sense to introduce *new* caseless matching algorithms for "compatibility" with existing web content. When boiled down to the actual use cases we're talking about (i.e. radio button name attribute matching), I think adding new functionality is what is in fact odious. ;) -- You are receiving this mail because: You are on the CC list for the bug.
Received on Wednesday, 12 February 2014 04:50:15 UTC