W3C home > Mailing lists > Public > public-svg-wg@w3.org > July to September 2014

RE: <tspan> and getBBox()

From: Smailus, Thomas O <Thomas.O.Smailus@boeing.com>
Date: Mon, 29 Sep 2014 21:45:29 +0000
To: Cameron McCormack <cam@mcc.id.au>, SVG WG <public-svg-wg@w3.org>
Message-ID: <175A0EE510663A46ACD5FF1A03AD46F5145F86@XCH-BLV-204.nw.nos.boeing.com>
Excellent.  I wonder how <tspan /> got hosed in SVG 1.1 SE, but that's water under the bridge.  
Boeing has a HUGE usecase for tspan having getBBox().

Thomas
--
Thomas Smailus, Ph.D.  P.E.
Boeing Information Technology
thomas.o.smailus@boeing.com

-----Original Message-----
From: Cameron McCormack [mailto:cam@mcc.id.au] 
Sent: Monday, September 29, 2014 14:42
To: Smailus, Thomas O; SVG WG
Subject: Re: <tspan> and getBBox()

Hi Thomas,

On 30/09/14 06:16, Smailus, Thomas O wrote:
> In SVG 1.1  <text /> implements SVGTextPositioningElement and 
> SVGTransformable (which in turn implments SVGLocatable and thus gives 
> <text/> getBBox() )
>
> <tspan /> doesn't implement SVGTransformable
>
> I see in the SVG 2 draft spec indicates "SVG 2 will allow transforms 
> on 'tspan'" (http://www.w3.org/TR/SVG2/text.html#TSpanElement ).
>
> Does this mean that <tspan /> will implement SVGTransformable and 
> finally get the much needed getBBox() function/method?

Yes, effectively.

> SVGTSpanElement  interface should inherit from SVGTransformable in 
> that case, correct?

The SVGTransformable interface was dropped in SVG 2 as part of moving to Web IDL (which doesn't allow multiple inheritance).  Its functionality is now all on SVGGraphicsElement, which SVGTSpanElement inherits from through SVGTextContentElement.
Received on Monday, 29 September 2014 21:46:08 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:20:20 UTC