W3C home > Mailing lists > Public > www-dom@w3.org > January to March 2001

RE: WD-DOM-Level-3-Core-20010126

From: <Mike.Champion@SoftwareAG-USA.com>
Date: Mon, 29 Jan 2001 09:39:40 -0500
Message-ID: <80B2BC83D9C0D411AE7D0050BAB106DD437231@sunshine.softwareag-usa.com>
To: www-dom@w3.org


> -----Original Message-----
> From: www-dom-request@w3.org 
> [mailto:www-dom-request@w3.org]On Behalf Of
> Michael Krivoruchko
> Sent: Sunday, January 28, 2001 4:51 PM
> To: www-dom@w3.org
> Subject: Re: WD-DOM-Level-3-Core-20010126
> 

>   > textContent
>   the attribute is one of possible rendering results. It will be
>   just impossible to please all applications even if the attribute
>   will be replaced by the method with a few arguments.
>   Should DOM provide an attribute/method which address very limited
>   amount of cases? 


Yes, because the objective is please many common applications, not all
applications.  The fact that the "value" property is undefined on Element
causes much confusion, and many DOM implementations provide some sort of
"Text node amelioration" convenience method to get the value.  The objective
here is simply to standardize common practice. 
Received on Monday, 29 January 2001 09:39:27 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 22 June 2012 06:13:48 GMT