W3C home > Mailing lists > Public > www-svg@w3.org > December 2005

SVGT 1.2: textContent is not compliant with DOM3 Core version

From: Maciej Stachowiak <mjs@apple.com>
Date: Mon, 26 Dec 2005 22:24:30 -0700
Message-Id: <0DF70C99-0D7F-4BFC-8774-E15933DFA2F8@apple.com>
To: www-svg@w3c.org

SVGT 1.2 says:

"textContent must be supported on all non-svg elements. For elements  
defined within this specification (see list of elements) textContent  
must be supported on the Text Content, 'desc', 'title' and 'metadata'  
elements. textContent on elements that do not support textContent is  
null. Setting textContent on an element that do not support  
textContent has no effect. "

This conflicts with the DOM Level 3 definition, which requires  
textContent on any Element, and requires it to return empty string  
when there is no text content. Returning null is not allowed. It  
sounds like DOM Level 3's textContent would be compliant with the SVG  
uDOM version, since it is not expressly forbidden to support  
textContent on any element.

But  the converse is not the case. This could cause problems for  
scripts authored against the uDOM running against a full DOM  

I recommend removing the limitations on textContent.

I recommend quoting verbatim or better yet normatively referencing  
the DOM Level 3 Core definition.

Received on Tuesday, 27 December 2005 06:28:52 UTC

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