- From: Cameron McCormack <cam@mcc.id.au>
- Date: Tue, 15 Mar 2011 10:22:35 +1300
- To: Robert O'Callahan <robert@ocallahan.org>
- Cc: "Tab Atkins Jr." <jackalmage@gmail.com>, Dean Jackson <dino@apple.com>, public-fx@w3.org
Robert O'Callahan: > OK, that implies a hard requirement that arbitrary CSS rules be able to > override any SVG attribute value. Whatever syntax you choose, that means > effectively minting a lot of new properties. Someone should make a list of > all the new properties that will be needed. Patrick made a list of SVG attributes he would like to see animatable from CSS: http://www.w3.org/Graphics/SVG/WG/wiki/F2F/Auckland_2011/CSS_Animation#Regular_Attributes That’s about 45 of them (assuming we mash together all attributes with the same name into a single property). The list seems reasonable at first glance. Initially I was in favour of promote *all* SVG attributes that are defined to be animatable, just so that authors didn’t have to worry about which ones are animatable (yet) and which aren’t. Other people on the FX call today seemed in favour of the staging approach, where we take a subset of the attributes (like Patrick’s list) to limit the work we need to do initially. -- Cameron McCormack ≝ http://mcc.id.au/
Received on Monday, 14 March 2011 21:23:23 UTC