- From: Ken Stacey <ken@svgmaker.com>
- Date: Fri, 30 Nov 2012 15:52:52 +1000
- To: www-svg@w3.org
> (BTW, I couldn't find anywhere in SVG1.1 that explicitly says that child > elements of a graphical shape don't render... am I missing something?) The Content Model for each element lists what child elements are allowed. For rect, there are only animation elements and descriptive elements in the content model. Ken On 30/11/2012 2:47 PM, Doug Schepers wrote: > Hi, Nikos- > > On 11/29/12 11:32 PM, Nikos Andronikos wrote: >> On 30/11/2012 12:41 PM, Dirk Schulze wrote: > ... >>> >>> This is reasonable for HTML, but not for SVG. It needs a lot of >>> specification work either. >> >> Forgetting the comparisons between HTML and SVG, I think allowing a >> drawing element to establish a new viewport and being able to place >> objects within that viewport makes total sense for a graphics language. >> It's possible now, but this is a more elegant way of doing it imo. > > Thanks. > > I didn't mean to draw too close a comparison to HTML... this isn't > really analogous at all. > > The essence of my proposal (which isn't really original to me, BTW... > it's something I've heard numerous times before) is simply a new way of > grouping rendered elements. > > (BTW, I couldn't find anywhere in SVG1.1 that explicitly says that child > elements of a graphical shape don't render... am I missing something?) > > Regards- > -Doug >
Received on Friday, 30 November 2012 05:53:24 UTC