[whatwg] usemap="" and related issues
jonas at sicking.cc
Tue Dec 2 17:12:42 PST 2008
Jonas Sicking wrote:
> Ian Hickson wrote:
>> On Thu, 26 Jun 2008, Jonas Sicking wrote:
>>>> On Sat, 18 Aug 2007, Jonas Sicking wrote:
>>>>> Since ID is case sensitive everywhere else, I don't see a reason to
>>>>> an exception from that rule here. That seems to unnecessarily
>>>>> implementation as well as introduce weird inconsistencies for authors.
>>>> It already is inconsistent for usemap="". At least for legacy Web
>>>> content I don't think we can do much about it. At that point, I'd
>>>> rather just extend that to XHTML than to keep another difference.
>>> In mozilla for HTML we only look at the name attribute, and only do
>>> so case insensitively. For XHTML we only look at the id attribute,
>>> and are always case sensitive.
>>> We have had a number of bugs filed on id not working on HTML, (with
>>> most of them pointing at the XHTML spec as a reason it should work)
>>> but they all use the same casing for the usemap attribute and the id
>>> Do you have any data showing that using case sensitive matching for
>>> the id attribute would break compatibility with any pages?
>> I do not. It seems like something where being incompatible with what
>> IE does is unnecessary, though.
> I just did a little bit of testing, but it seems like IE *always* treat
> id's in a case insensitive manner, including for getElementById. If we
> are duplicating that quirk then we should do it consistently, not just
> for image maps.
> However I don't think we should.
Just wanted to point out that this part of the message never got replied to.
More information about the whatwg