W3C home > Mailing lists > Public > www-svg@w3.org > May 2011

Re: Filters spec: CSS vs SVG

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Mon, 9 May 2011 14:29:13 -0700
Message-ID: <BANLkTi=kg97z_VZQH2na+9zSRQQGYOCQDQ@mail.gmail.com>
To: Rik Cabanier <cabanier@gmail.com>
Cc: Dean Jackson <dino@apple.com>, Chris Lilley <chris@w3.org>, Erik Dahlstrom <ed@opera.com>, public-fx@w3.org, www-svg <www-svg@w3.org>
On Mon, May 9, 2011 at 10:48 AM, Rik Cabanier <cabanier@gmail.com> wrote:
> On Fri, May 6, 2011 at 5:54 PM, Dean Jackson <dino@apple.com> wrote:
>> I think all existing markup filters should remain and be available to all
>> content via the filter property.
>
> There was a discussion between you and Tab Atkins about this under the title
> 'generators in filters'.
> I thought the consensus was to move these to the image values module. Are
> you suggesting instead that they are available in images values and filters?

Yes, all existing filters should remain, as SVG filters.  In the CSS
syntax, they're accessible simply by the url() function.

However, the filters that are just image servers, like feTurbulence,
won't get a facelift as CSS functions in the Filters spec; instead,
they'll be part of the Image Values spec, which is the correct place
to define new image servers in CSS.  (Their current existence as SVG
Filters appears to be a historical accident, possibly as a result of
SVG not quite unifying its notion of what an image server is.)

~TJ
Received on Monday, 9 May 2011 21:32:07 GMT

This archive was generated by hypermail 2.3.1 : Friday, 8 March 2013 15:54:48 GMT