W3C home > Mailing lists > Public > public-fx@w3.org > January to March 2012

Re: CSS Animations and Transitions on SVG Attributes

From: Chris Lilley <chris@w3.org>
Date: Fri, 6 Jan 2012 15:23:07 +0100
Message-ID: <1008440363.20120106152307@w3.org>
To: Patrick Dengler <patd@microsoft.com>
CC: FX <public-fx@w3.org>, Dean Jackson <dino@apple.com>
On Thursday, January 5, 2012, 8:49:58 PM, Patrick wrote:

PD> For azimuth and elevation these are trickier and would like some
PD> input.  I?m not familiar enough with aural stylesheets to
PD> understand the frequency or usage  patterns of azimuth and
PD> elevation.  

Ignore those CSS properties. No-one uses them.

I say that with (a little) sadness since I played a part in specifying them, back in the day (and based on what VRML was doing at the time for positional audio) but aural stylesheets never took of or saw any adoption.

New work in that area [1] takes a different approach (one that is more likely to be implemented), separates speech styling from other auditory styling and does not use azimuth or elevation.

PD> While on the surface they appear to be innovative, I
PD> don?t have the data to understand their usage pattern or
PD> frequency.  

For the original use case see above. The frequency of use is easy - zero.

PD> If they were used frequently enough I would propose a
PD> name change to the SVG azimuth and elevation  attributes in a way
PD> that is backward compatible; and in fact that is the path I was by
PD> default going to take.  But if they are not, I would prefer to
PD> preserve the SVG name. 

Which is actually used in content.

PD> I think that of all of the filter
PD> attributes, azimuth and elevation are the most relevant  and prime
PD> for transitions and animations and which is why I am hesitant to change their names.

Right.

PD> Option #1
PD>  
PD> Deprecate azimuth and elevation from aural stylesheets and
PD> preserve azimuth and elevation as is in SVG.
PD>  
PD> Issue: I have neither knowledge nor wisdom as to whether this  is
PD> wise, agreeable, feasible or reasonable J

Its the only sensible option.
 
[1] http://dev.w3.org/csswg/css3-speech/

-- 
 Chris Lilley   Technical Director, Interaction Domain                 
 W3C Graphics Activity Lead, Fonts Activity Lead
 Co-Chair, W3C Hypertext CG
 Member, CSS, WebFonts, SVG Working Groups
Received on Friday, 6 January 2012 14:23:48 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 6 January 2012 14:23:49 GMT