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

Re: CSS Animations and Transitions on SVG Attributes

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Thu, 5 Jan 2012 12:23:35 -0800
Message-ID: <CAAWBYDDxrUfLW4zoLNLupSy1sLSmox=3TBoM4YW3ik-OrajVVA@mail.gmail.com>
To: Patrick Dengler <patd@microsoft.com>
Cc: FX <public-fx@w3.org>, Dean Jackson <dino@apple.com>, Daniel Weck <daniel.weck@gmail.com>
(I've reformatted this email into plain text, but have made zero
content changes.)

On Thu, Jan 5, 2012 at 11:49 AM, Patrick Dengler <patd@microsoft.com> wrote:
> I’ve been thinking through Dean’s objection to this proposal and my proposed recommendation, with which he did not agree.  This was with property name collisions:
>> I think a better idea would be to deal with Type and Element
>> collisions by creating a property with a new name, rather than
>> just sticking with the exact same name as the attribute.
> In speaking to more folks who have a better understanding of CSS than I do, I have a better understanding of this than I did before.  From my table of proposed attributes to be “promoted” the following had collisions:
> * azimuth -  Semantic and Type Collision w/ CSS aural azimuth Property. See Below
> * elevation - Semantic and Type Collision w/ CSS aural elevation property. See Below
> * offset - Element Collision (gradient and filter). Recommendation: Follow the Element Collision model. In the case of offset, it appears that adding support for percentage type to the filter attributes (RGB) for feComponentTransfer should be feasible.
> * transform - Larger issue being covered with a separate specification to rationalize CSS and SVG Transforms both 2D and 3D.  Dean noted that Webkit now has CSS Transforms applied to SVG. This is a great model that is worth adopting, even if it may or may not need further refinement.
> For azimuth and elevation these are trickier and would like some input.  I’m not familiar enough with aural stylesheets to understand the frequency or usage patterns of azimuth and elevation.  While on the surface they appear to be innovative, I don’t have the data to understand their usage pattern or frequency.  If they were used frequently enough I would propose a name change to the SVG azimuth and elevation attributes in a way that is backward compatible; and in fact that is the path I was by default going to take.  But if they are not, I would prefer to preserve the SVG name. I think that of all of the filter attributes, azimuth and elevation are the most relevant and prime for transitions and animations and which is why I am hesitant to change their names.
> Option #1
> Deprecate azimuth and elevation from aural stylesheets and preserve azimuth and elevation as is in SVG.
> Issue: I have neither knowledge nor wisdom as to whether this is wise, agreeable, feasible or reasonable J
> Option #2
> Add azimuthDistance and evelationDistance as presentation attributes (and properties) to feDistantLIght.
> Issue:  This is a departure from SVG 1.1 and a departure from an otherwise relatively flat and well named attribute

I suggest pinging Daniel Weck, the editor of CSS3 Speech.  I've cc'd
him with this message.

Received on Thursday, 5 January 2012 20:24:23 UTC

This archive was generated by hypermail 2.3.1 : Monday, 22 June 2015 03:33:46 UTC