Re: [SVGMobile12] A.2.8 Text Node Access

These are good suggestions and we have changed the spec as you suggest.
The 'tspan' paragraph you refer to is changed to:
"The result of getting and setting text content via the #text mechanism
is exactly the same as when using the textContent attribute. Therefore
the user should be aware of the fact that styling by child 'tspan'
elements (i.e. 'tspan' elements that are children of the element which
text content is retrieved) will be lost if a text string is retrieved
from an element and then set back again."
Thanks for your thorough review, please let us know shortly if this does
not address your concerns.

From: Jonathan Watt <> 
Date: Tue, 24 Jan 2006 17:55:20 +0000
Message-ID: <> 

Dear SVG WG, section
uses the phrase "text node" both in the section title and in it's
However, section
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
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
   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
'tspan' element's parent.


Received on Monday, 13 March 2006 13:54:50 UTC