W3C home > Mailing lists > Public > www-svg@w3.org > November 2012

Re: Proposal: Nesting SVG Graphics Elements

From: Rik Cabanier <cabanier@gmail.com>
Date: Fri, 30 Nov 2012 08:38:00 -0800
Message-ID: <CAGN7qDAc8kad2w04OFVnN-eZxeXjMYUMz6OuuQ0ePQRT4RZA6w@mail.gmail.com>
To: Cameron McCormack <cam@mcc.id.au>
Cc: Dirk Schulze <dschulze@adobe.com>, "Tab Atkins Jr." <jackalmage@gmail.com>, "steve@fenestra.com" <steve@fenestra.com>, SVG public list <www-svg@w3.org>
On Thu, Nov 29, 2012 at 11:08 PM, Cameron McCormack <cam@mcc.id.au> wrote:

> Rik Cabanier:
>  do you think extending the box model to SVG will make it faster to render?
>> As soon as you allow <rect><text>..</text></rect>, people are going to
>> want that rect to fit the text.
> Obviously it will take some computation to apply CSS layouts to SVG
> content, but I wouldn't want content that doesn't use it to be slower.
> Whether the <rect><text>...</text></rect> syntax makes the rect fit the
> text (as I understand Doug's proposal it doesn't), it makes a lot of sense
> to me to be able to have a rectangle sized according to some text.  SVG
> diagrams now just don't respond well different fonts available, localised
> text, available space for rendering, etc.

Maybe it doesn't, but judging by Tab's reaction, that is the first thing
that people are going to want.
They will want sizing/fitting/clipping of parents and children.

As others in this thread have remarked, this is also changing the semantics.


implies that the rect contains the text.
Received on Friday, 30 November 2012 16:38:29 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:29:53 UTC