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

[SVGMobile12] Comments: Text

From: T Rowley <tor@cs.brown.edu>
Date: Wed, 18 May 2005 20:02:48 -0500
Message-ID: <428BE5B8.8030209@cs.brown.edu>
To: www-svg@w3.org

10.2

"It is possible to apply a gradient to text.  ... object bounding box 
units are computed relative to the entire 'test' element in all cases..."

Why have text behave different that other geometry (11.12)?

10.6.1

"Many of the features here go beyond the functionality provided by the 
elements in this profile..."

This "tiny" specification is almost 400 pages - leave out verbarge not 
associated with the specification in question.

10.11

<textArea> needs an example or two.

10.11.1

"For cases where box model layout is required, it is suggest that a 
'foreignObject'..."

Section 10.1 says that "the exact semantics of this approach are not 
completely defined."

10.11.1

"The layout of wrapped text is user agent dependent..."

Not good for interoperability, especially in light of having SVG defined 
fonts.  Perhaps a "wrapping = auto | exact" attribute is needed, in the 
same fashion that textPath in SVG full has a spacing attribute?

10.12

It seems one of the natural uses that editable text fields might be put 
to is input fields, but there seems to be no way to control the "width" 
of a field or clip over-long content (as SVGT lacks both <clipPath> and 
nested <svg>).

10.12.1

"For WYSIWYG editing the following..."

What should happen if current point is moved to an area not visible 
(overlapping geometry, text running outside the outer <svg>, etc)?
Received on Thursday, 19 May 2005 01:04:33 GMT

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