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

Re: Filter Templates

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Thu, 24 Feb 2011 15:06:15 -0800
Message-ID: <AANLkTinVJyX99zp7fZezx8HU837BSemO2SbqL8OWtjma@mail.gmail.com>
To: robert@ocallahan.org
Cc: Rik Cabanier <cabanier@gmail.com>, Rik Cabanier <cabanier@adobe.com>, Cameron McCormack <cam@mcc.id.au>, Brad Kemper <brad.kemper@gmail.com>, www-style list <www-style@w3.org>, "public-fx@w3.org" <public-fx@w3.org>, Dean Jackson <dino@apple.com>
On Thu, Feb 24, 2011 at 2:54 PM, Robert O'Callahan <robert@ocallahan.org> wrote:
> On Fri, Feb 25, 2011 at 10:25 AM, Dean Jackson <dino@apple.com> wrote:
>> On Feb 24, 2011, at 12:43 PM, Rik Cabanier wrote:
>> the CSS could look like:
>>    filter: url(dropshadow.pbk) param1 param2;
>> For transitions or animations, the parameters would be allowed to change.
>> Rik
> If we're going to refer to external resources that define complex filters,
> why not just build on top of SVG filters?

Agreed; CSS filters are meant to be for simple, easy filters.  They're
defined on top of SVG for simplicity/reuse, is all.  We explicitly do
*not* want to pull in the full power of SVG filters, as that's what
SVG is for.

Received on Thursday, 24 February 2011 23:09:22 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:49:38 UTC