W3C home > Mailing lists > Public > public-html@w3.org > April 2009

Re: Selectors, getElementsByTagName() and camelCase SVG

From: Anne van Kesteren <annevk@opera.com>
Date: Fri, 03 Apr 2009 17:10:27 +0200
To: "Boris Zbarsky" <bzbarsky@mit.edu>
Cc: "Henri Sivonen" <hsivonen@iki.fi>, "HTML WG" <public-html@w3.org>, www-svg <www-svg@w3.org>
Message-ID: <op.urtgfpxj64w2qv@annevk-t60.oslo.opera.com>
On Fri, 03 Apr 2009 15:29:20 +0200, Boris Zbarsky <bzbarsky@mit.edu> wrote:
> Anne van Kesteren wrote:
>> How about we change getElementsByClassName() to do this:
> I assume you meant getElementsByTagName

Yeah, oops.

>>   1. Let asciilowercasetoken be the result of lowercasing token.
>>   2. Iterate through the DOM and return elements which:
>>       a. Have the HTML namespace and whose localName is identical
>>         to asciilowercasetoken.
>>      b. localName is identical to token.
>>  This would work well for Selectors too I think. You would never match  
>> createElementNS(HTML namespace,"IMG"), but that element does not have  
>> actual <img> semantics anyway and is something people would never do.
> This is basically my proposal #2, and is the minimal change to what  
> Gecko and Webkit currently do to give sane behavior for camelCase SVG in  
> This would, in fact, be my top choice for how this should all work.

Great! I think this gives the least amount of magic and most predictable  
model to authors, while not requiring UAs to perform string comparison.

Anne van Kesteren
Received on Friday, 3 April 2009 15:11:19 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:15:44 UTC