- From: Anthony Grasso <Anthony.Grasso@cisra.canon.com.au>
- Date: Tue, 15 Mar 2011 22:31:31 +0000
- To: Tab Atkins Jr. <jackalmage@gmail.com>
- CC: Dean Jackson <dino@apple.com>, "public-fx@w3.org" <public-fx@w3.org>, "robert@ocallahan.org" <robert@ocallahan.org>
> -----Original Message----- > From: public-fx-request@w3.org [mailto:public-fx-request@w3.org] On > Behalf Of Tab Atkins Jr. > Sent: Wednesday, 16 March 2011 8:38 AM > To: robert@ocallahan.org > Cc: Dean Jackson; public-fx@w3.org > Subject: Re: CSS Animations Targeting SVG attributes > > Since we're omitting the <filter>-related attributes due to CSS > Filters, perhaps we could omit the gradient-related attributes due to > CSS Gradients? CSS and SVG gradients have a trivial mapping, albeit > not one that can be expressed directly in CSS. > Gradient-related Properties are still in the list - which is fine. For the following properties "linearGradient" should be added to the element list: x1, x2, y1 and y2 For the following properties "radialGradient" should be added to the element list: cx, cy and r > Taking these suggestions would let us introduce less than 20 new > properties, total. Given that you're pretty keen to map attributes to properties, do you intend on presenting both options (1. Mapping attributes, 2. Targeting attributes with attr())to the CSS Working Group? The information contained in this email message and any attachments may be confidential and may also be the subject to legal professional privilege. If you are not the intended recipient, any use, interference with, disclosure or copying of this material is unauthorised and prohibited. If you have received this email in error, please immediately advise the sender by return email and delete the information from your system.
Received on Tuesday, 15 March 2011 22:32:07 UTC