Re: CSS Animation and Transitions on SVG attributes

The point being that potentially these all end up as properties in CSS?

I strongly think they should get prefixed, for two reasons:
1. Avoiding conflict with existing and future CSS properties.
2. Making CSS easier to understand; if I were reading some random CSS file and stumbled across a property called 'r', I'd b e scratching my head and wondering what the heck it meant. 'svg-r' would help.

Simon

On Feb 21, 2012, at 8:56 AM, Patrick Dengler wrote:

> Hi folks,
>  
> I wanted to ping one more time about the list of issued identified in creating the proposal for CSS Animations on SVG.  The the issues and proposed recommendations are listed in this text sent out on Feb 7th. I wasn’t sure if it was lost in the shuffle or just simple (cross my fingers) well thought out and acceptable J.  I believe Erik and Chris have also tried to get some response.  In either event, it would be great to see if we can close on this, or whether we need more issues to resolve.  In the meantime, I am going to make the edits to the SVG Specification.
>  
> -Patrick Dengler
> Microsoft
>  
> RE: http://lists.w3.org/Archives/Public/www-style/2012Feb/0333.html
>  
>  
>  
> I was responsible for providing the list of presentation attributes that the SVG Working Group has resolved to be the proposed set for inclusion in CSS Animations.  This list is included here:
>  
> amplitude
> azimuth
> bias
> cx,cy
> diffuseConstant
> divisor
> dx
> dy
> elevation
> exponent
> fx
> fy
> height,width
> intercept
> k1,k2,k3,k4
> limitingConeAngle
> numOctaves
> offset
> pointsAtX,pointsAtY, pointsAtZ
> r
> radius
> rx,ry
> scale
> slope
> specularConstant
> specularExponent
> startOffset
> stdDeviation
> surfaceScale
> targetX,targetY
> transform
> x,y
> x1,x2,y1,y2
> z
>  
>  
>