W3C home > Mailing lists > Public > www-dom@w3.org > April to June 2011

Re: Setting Node.textContent to null

From: Ms2ger <ms2ger@gmail.com>
Date: Tue, 28 Jun 2011 23:50:45 +0200
Message-ID: <4E0A4CB5.8020104@gmail.com>
To: www-dom@w3.org
On 06/28/2011 09:09 PM, David Flanagan wrote:
> The textContent of Node has nullable type DOMString? because some node
> types do not have text content and return null when this attribute is
> queried.
> This means, however, that as far as IDL is concerned, it is legal to set
> the attribute to null on a node, and DOMCore needs to specify what
> happens when textContent is set to null for an Element, DocumentFragment
> or PI. (The Text and Comment cases are okay because CharacterData.data
> is declared [TreatNullAs=EmptyString].)
> It seems obvious that the right thing to do is to treat null as an empty
> string, but I don't think that you can declare the attribute
> [TreatNullAs=EmptyString] since that would alter the return value for
> node types that do not have text content, wouldn't it?

I attempted to clarify this; it's currently specified to match WebIDL in 
converting null to "null".


I hope this is better
Received on Tuesday, 28 June 2011 21:51:24 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 20 October 2015 10:46:17 UTC