W3C home > Mailing lists > Public > www-svg@w3.org > January 2006

[SVGMobile12] A.2.8 Text Node Access

From: Jonathan Watt <jwatt@jwatt.org>
Date: Tue, 24 Jan 2006 17:55:20 +0000
Message-ID: <43D66A08.2050804@jwatt.org>
To: www-svg@w3.org

Dear SVG WG,

http://www.w3.org/TR/SVGMobile12/svgudom.html#Text_Node_Access section A.2.8
uses the phrase "text node" both in the section title and in it's contents.
However, http://www.w3.org/TR/SVGMobile12/svgudom.html#dom::Node section A.3.2
states that:

   Node types that must be supported in the uDOM are Element nodes
   and Document nodes.

There is no requirement to support Text nodes so please keep the Tiny spec free
of references to "text node", "Text node", "Text Node" or whatever else to avoid
confusion. Instead use "an element's textual content" or some other suitable
phrase. I suggest changing section A.2.8 to start with something along the lines of:

   A.2.8 Text Content Access

   In the SVG uDOM, there are two alternative ways to access an element's
   textual content. A special means of text access via the TraitAccess
   interface is available...

Also note a few paragraphs further down contains the text:

   Therefore the user should be aware of the fact that styling
   by 'tspan' elements will be lost if she gets a text string
   from the model and sets it back again.

Please make this clear that the text is referring to using the model on the
'tspan' element's parent.

Received on Tuesday, 24 January 2006 17:58:17 UTC

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