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

Re: SVG12: #text traits

From: Bjoern Hoehrmann <derhoermi@gmx.net>
Date: Mon, 23 May 2005 01:40:24 +0200
To: Robin Berjon <robin.berjon@expway.fr>
Cc: www-svg@w3.org
Message-ID: <42991569.105185218@smtp.bjoern.hoehrmann.de>

* Robin Berjon 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.

This does not satisfy me, at the very least this clarification should be
added to the draft. The #text trait is not defined in JSR-226 as far as
I can tell, it's only noted in the support table where it is only
supported for text elements and not for tspan (which is not supported at
all, it seems), desc, title, metadata, etc. So there is basically no
compatibility here that could be gained.

There are also many other incompatibilities, the clarifications for
SVGElement.id for example are not in JSR-226 and it uses confusing
legacy methods like addEventListener which are not added to SVG Tiny 1.2
either, so there is virtually nothing to be gained here. Please
coordinate with the Expert Group instead of having such legacy methods
and incompatibilities. Clearly the Working Group made them aware that
it is inappropriate to cite SVG Tiny 1.2 as other than work in progress,
so this should not be a problem at all.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Weinh. Str. 22 · Telefon: +49(0)621/4309674 · http://www.bjoernsworld.de
68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 
Received on Sunday, 22 May 2005 23:39:40 GMT

This archive was generated by hypermail 2.3.1 : Friday, 8 March 2013 15:54:30 GMT