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

Re: Selectors, getElementsByTagName() and camelCase SVG

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Thu, 02 Apr 2009 21:00:16 -0400
Message-ID: <49D55FA0.1020901@mit.edu>
To: HTML WG <public-html@w3.org>, www-svg <www-svg@w3.org>
Cameron McCormack wrote:
> 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?

Per the current HTML5 spec text:

createElement: In an text/html document, this always creates an element 
whose namespace is the XHTML1 namespace and whose localName is the 
ascii-lowercased string passed to createElement.

createElementNS: As per DOM Core spec: Creates an element in the given 
namespace and with the given localName.  No case conversion is performed.

getElementsByTagName called on a Document object that was served as 
text/html, or on an element in the XHTML1 namespace in such a document: 
A node matches if one of the conditions below holds:
   1) Its tagName exactly matches the string passed in.
   2) It is a node in the XHTML1 namespace and its tagName matches
      the string passed in when an ASCII-case-insensitive comparison
      is done.

getElementsByTagName in all other cases: As per DOM Core spec.  No case 
conversions are performed.

getElementsByTagNameNS: As per DOM Core spec.  No case conversions are 

Selectors: This section is still to be written.

Was that the question?  Or were you asking about the two proposals to 
modify this?

Received on Friday, 3 April 2009 01:01:00 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 March 2017 09:47:17 UTC