- From: Erik Dahlstrom <ed@opera.com>
- Date: Fri, 12 Mar 2010 08:49:56 +0100
- To: "L. David Baron" <dbaron@dbaron.org>
- Cc: "public-fx@w3.org" <public-fx@w3.org>, www-svg <www-svg@w3.org>
On Thu, 11 Mar 2010 23:23:50 +0100, L. David Baron <dbaron@dbaron.org> wrote: > On Thursday 2010-03-11 19:48 +0100, Erik Dahlstrom wrote: >> Here are some possible ways of adding support for css transforms in svg: >> >> 1. Treat it as any of the other CSS properties that SVG share with >> HTML/CSS (e.g 'display'), basically same as overriding the attribute >> Advantage(s): mostly consistent with the model (possibly with the >> exception of 'none') >> Notes: What 'transform: none' means in css2d transforms isn't >> clearly defined, for svg it would have to mean that the attribute is >> used, otherwise backwards compatibility is lost. Should there be an >> 'auto' initial value to deal with these cases? > > Why would backwards-compatibility be lost in these cases? I'd think > that even without changing 'none', things would be fine, since CSS > cascading says that any specified CSS overrides the SVG attribute, > but if there's no specified CSS, then the SVG attribute wins (just > like for other properties). Yes, that's the point Anne was making too. My concern there is fully addressed by this, thanks. /Erik -- Erik Dahlstrom, Core Technology Developer, Opera Software Co-Chair, W3C SVG Working Group Personal blog: http://my.opera.com/macdev_ed
Received on Friday, 12 March 2010 07:44:24 UTC