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

Re: Updated filters specification

From: Rik Cabanier <cabanier@gmail.com>
Date: Mon, 18 Apr 2011 21:23:57 -0700
Message-ID: <BANLkTimq=diAb85oYgUZR1sPOFyd-F+m5g@mail.gmail.com>
To: Dean Jackson <dino@apple.com>
Cc: public-fx@w3.org
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...

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.

3. DropShadow filter
I see that you included a dropshadow filter (thank you!). Is there a reason
you didn't include it in the list of the filter functions?

Rik

On Mon, Apr 18, 2011 at 6:39 AM, Dean Jackson <dino@apple.com> wrote:

> As promised (but late! sorry) here is an updated Filters specification.
> We've moved to Mercurial, so forgive the complex URL:
>
>
> https://dvcs.w3.org/hg/FXTF/raw-file/07eb4eb9f3ed/filters/publish/Filters.html
>
> Or for the latest version, whatever that may be at the time you click:
>
> https://dvcs.w3.org/hg/FXTF/raw-file/tip/filters/publish/Filters.html
>
> I've included a ChangeLog, but in general the changes are:
>
> - renamed the main file (removing "svg")
>
> - temporarily comment out reqs and primer publications
>  (I'm not sure these are needed any more)
>
> - update the intro section to be more language neutral
>
> - define the filter property in terms of a list of functions
>  which is a space separated list of commands like url(), sepia() etc
>
> - define the most useful shorthand functions and show the equivalent
>  <filter> version for each shorthand function. I only picked the functions
>  that have an equivalent at the moment. Future versions may include
>  more shorthands, which may mean more <fe*> operators.
>  Note: definitions of "useful" may differ. I don't consider the
>  lighting functions terribly useful, but they can be easily added if
>  requested.
>
> I've also put a big warning in the CVS version pointing at this new spec.
>
> I realise there isn't a call today, so please bombard the list with
> comments and complaints.
>
> Dean
>
>
>
Received on Tuesday, 19 April 2011 04:24:24 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 April 2011 04:24:24 GMT