[Bug 16970] i18n-ISSUE-105: compatibility caseless matching


--- Comment #7 from John Daggett <jdaggett@mozilla.com> ---
Addison, the terminology "compatibility caseless manner" implies that it's
needed to be compatible with existing implementations but there's no
consistency to be compatible with. The results for radio button name attribute
matching, etc. will be different across IE/Gecko/Webkit-derivative (and across
OS with IE). So I think it would actually be smarter here to eliminate the
"compatibility caseless" definition and specify ASCII-case-insensitive, since
that's simpler to standardize on for these specific, isolated instances.

Basically, I think comment 2 is wrong, you don't get any sort of compatibility
by using what is defined to be "compatibility caseless" matching here.  I
suspect that there wouldn't be much web content that would be broken by
specifying ASCII-case-insensitive matching here, since the only way a site can
currently work across browsers is to limit themselves to

You are receiving this mail because:
You are on the CC list for the bug.

Received on Wednesday, 12 February 2014 02:19:49 UTC