W3C home > Mailing lists > Public > www-svg@w3.org > April 2009

Re: Selectors, getElementsByTagName() and camelCase SVG

From: Cameron McCormack <cam@mcc.id.au>
Date: Fri, 3 Apr 2009 11:14:39 +1100
To: Jonas Sicking <jonas@sicking.cc>
Cc: Boris Zbarsky <bzbarsky@mit.edu>, Henri Sivonen <hsivonen@iki.fi>, HTML WG <public-html@w3.org>, www-svg <www-svg@w3.org>
Message-ID: <20090403001439.GC22657@arc.mcc.id.au>
Jonas Sicking:
> > I think there are three obvious options here:
> >
> > 1)  What the spec currently has.
> > 2)  What Gecko/Webkit currently do.
> > 3)  Having createElementNS(xhtml_ns, str) ascii-lowercase str in HTML
> >      (but not XHTML, of course) documents, then do what Gecko/Webkit
> >      currently do.
> >
> > Is there a reason to not take approach 3?
> 
> I really like option 3 here. It makes things very consistent in that
> HTML elements in a HTML document are case insensitive through and
> through. And HTML element would be defined as any element in xhtml_ns.

Apologies for not paying enough attention, here.  What is the current
suggestion for handling camel-cased SVG elements in
createElement{,NS}(), getElementsByTagName{,NS}() and Selectors?

-- 
Cameron McCormack ≝ http://mcc.id.au/
Received on Friday, 3 April 2009 00:15:44 GMT

This archive was generated by hypermail 2.3.1 : Friday, 8 March 2013 15:54:42 GMT