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

Re: Updated filters specification

From: Erik Dahlstrom <ed@opera.com>
Date: Tue, 19 Apr 2011 10:22:21 +0200
To: "Dean Jackson" <dino@apple.com>, "Rik Cabanier" <cabanier@gmail.com>
Cc: public-fx@w3.org
Message-ID: <op.vt6evjv0geuyw5@localhost>
On Tue, 19 Apr 2011 06:23:57 +0200, Rik Cabanier <cabanier@gmail.com>  

> Hi Dean,
> This looks very good!
> A couple of questions:
> 1. Filter region extensions.
> Why do you need to specify this? I can see that this is necessary for
> certain types of filters, but for the most common ones, the browser can  
> just
> calculate if for you.
> Could this be optional? It will for sure make author's life easier...

Yeah, that's been discussed before, and they're going away, I have an  
action to remove that (it's basically leftovers from an old SVG 1.2 Full  

> 2. Accessing the background image
> Would there ever be a reason to do this? This seems like a very expensive
> operation that could be worked around by rearranging the content.

You're right that it can be expensive to generate. I think in some (rare?)  
scenarios it is necessary to have something like enable-background. There  
is also the SVG 1.1 backwards compatibility aspect to consider. Feel free  
to elaborate on how an alternative to enable-background would look like.

I think that the optional <x>,<y>,<width>,<height> values in  
'enable-background' should be deprecated, because they are useless in  
practice. We should let the UA compute the necessary background buffer  
region, and just ignore these values if specified.

Erik Dahlstrom, Core Technology Developer, Opera Software
Co-Chair, W3C SVG Working Group
Personal blog: http://my.opera.com/macdev_ed
Received on Tuesday, 19 April 2011 08:23:25 UTC

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