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

Re: SVG12: #text traits

From: Robin Berjon <robin.berjon@expway.fr>
Date: Thu, 19 May 2005 11:48:36 +0900
Message-ID: <428BFE84.3010207@expway.fr>
To: Bjoern Hoehrmann <derhoermi@gmx.net>
Cc: www-svg@w3.org

Dear Björn,

Bjoern Hoehrmann wrote:
>   From http://www.w3.org/TR/2005/WD-SVGMobile12-20050413/svgudom.html
> section A.2.7 "The result of getting and setting text content via the
> #text mechanism is exactly the same as when using the textContent
> attribute." This means that this feature is redundant. Please either
> explain in detail why it is not redundant and give advice as to when
> which of these methods should be used or remove the feature from the
> draft to easy implementation, testing, etc.

This is a case in which we've had to concede to redundancy in order to 
obtain compatibility. The #text trait is what is defined in JSR-226, and 
textContent is the field inherited from DOM 3 Core — we have resolved to 
support both as we wish to be compatible with both.

If you are using the uDOM and don't intend to be compatible with JSR-226 
(either because you're already using features not present there, or 
because you're not using Java), then the recommended one is textContent. 
In all other situations, #text is best.

Robin Berjon
   Research Scientist
   Expway, http://expway.com/
Received on Thursday, 19 May 2005 02:48:36 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:54:06 UTC