W3C home > Mailing lists > Public > public-fx@w3.org > April to June 2011

Re: Filters spec: CSS vs SVG

From: Rik Cabanier <cabanier@gmail.com>
Date: Wed, 4 May 2011 14:29:45 -0700
Message-ID: <BANLkTikJzZ7LrDW+VjcLFDRFso2oSLa60A@mail.gmail.com>
To: Erik Dahlstrom <ed@opera.com>
Cc: public-fx@w3.org, www-svg <www-svg@w3.org>
Thank Erik!
I didn't know that this was a replacement for the current spec.

So far, I think these are the following proposed changes:
- remove section 6, the filter effects region
- remove backgound-image and background-alpha
- remove section on the enable-background keyword
- change default behavior of an unknown filter to 'ignore' instead of the
'null filter'
- remove filters that create an image and move them to the image-values spec
(ie feTurbulence)
- remove the feComposite filter and replace with the CSS/SVG compositing


On Wed, May 4, 2011 at 4:41 AM, Erik Dahlstrom <ed@opera.com> wrote:

> On Tue, 03 May 2011 20:30:05 +0200, Rik Cabanier <cabanier@gmail.com>
> wrote:
>  All,
>> in yesterday's meeting is sounded that the CSS Filter spec is going to
>> affect the regular (non-CSS) SVG filter spec as well.
>> Did I understand this correctly?
> It's "Filter Effects 1.0", and the spec can be found here:
>  https://dvcs.w3.org/hg/FXTF/raw-file/tip/filters/publish/Filters.html
> As agreed in earlier discussions in the taskforce we're making one spec. It
> includes both SVG and CSS definitions.
>  If so and we remove/change filters or features from the filters proposal,
>> is
>> someone going to update the SVG filters?
> No, the Filter Effects 1.0 spec replaces the SVG Filters 1.2 spec.
>  I was under the impression that we were going to leave SVG filters (and
>> compositing) alone and define a new simpler proposal that would only apply
>> to CSS styled HTML and SVG content.
> We are defining a simpler syntax for filter effects, however I'm not
> convinced it's a good idea to ignore SVG Filters which are widely
> implemented at this stage, and considering that diverging from that
> potentially makes it harder to reuse existing code.
> The general idea so far has been: use svg <filter> markup for the more
> complex filter effects, use css shorthands for simple filter effects.
> --
> Erik Dahlstrom, Core Technology Developer, Opera Software
> Co-Chair, W3C SVG Working Group
> Personal blog: http://my.opera.com/macdev_ed
Received on Wednesday, 4 May 2011 21:30:14 UTC

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