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

Re: [filters] Reusing filter functions as <image>s in CSS

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Thu, 19 May 2011 09:57:08 -0700
Message-ID: <BANLkTikF49xTbFLFsChzzFb0TAbhNujOhQ@mail.gmail.com>
To: Brad Kemper <brad.kemper@gmail.com>
Cc: "robert@ocallahan.org" <robert@ocallahan.org>, "public-fx@w3.org" <public-fx@w3.org>
On Thu, May 19, 2011 at 12:05 AM, Brad Kemper <brad.kemper@gmail.com> wrote:
> On May 18, 2011, at 11:43 PM, "Tab Atkins Jr." <jackalmage@gmail.com> wrote:
>> On Wed, May 18, 2011 at 7:48 PM, Robert O'Callahan <robert@ocallahan.org> wrote:
>>> How about a new image value "filter(image, list of filters)"?
>>
>> Why didn't I think of that?  That's a pretty good answer.
>
> In addition to a filter property?

The 'filter' property takes, as its original input, the element
itself.  The filter() function instead takes the passed image as the
original input.

Using filter() instead of 'filter' would require some way to refer to
the element itself as an image (not necessarily a blocker - we already
have element() which does basically this), and some probably-confusing
interaction with 'content', like:

.blur-me {
  content: filter(contents, blur(5px));
}

Animating filters would then require that 'content' itself be
animatable, which may or may not be weird.

~TJ
Received on Thursday, 19 May 2011 16:57:56 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 19 May 2011 16:57:57 GMT