W3C home > Mailing lists > Public > public-fx@w3.org > July to September 2011

Re: Updated Filters 1.0 editor's draft

From: Dean Jackson <dino@apple.com>
Date: Wed, 31 Aug 2011 05:40:58 +1000
Cc: public-fx@w3.org
Message-id: <5576BFDD-2AA6-46B2-9019-4461803AA1D2@apple.com>
To: "Tab Atkins Jr." <jackalmage@gmail.com>

On 31/08/2011, at 2:17 AM, Tab Atkins Jr. wrote:

> On Mon, Aug 29, 2011 at 5:34 PM, Dean Jackson <dino@apple.com> wrote:
>> - Added drop-shadow shorthand
> 
> Elika and I have been advocating an approach for functions where, when
> possible, the contents are just normal CSS values.  Explicit
> comma-separated argument lists should only be used when necessary for
> disambiguation.  In particular, this would mean that blur() can
> probably drop the commas and just accept one or two space-separated
> lengths, and drop-shadow() can drop the commas and just use <shadow>,
> perhaps with a restriction that you can't provide the 'input' keyword
> (text-shadow does this).  Gamma and unsharp can potentially drop the
> commas as well.

Sure. I'll make those changes.

> As a sidenote, while I understand the historic reasoning behind the
> name of the unsharp() function, it's really super-confusing to have
> something that sharpens an image be named "unsharp".  Could we change
> this to just "sharpen" or something?

Yes, I think that makes sense too.

Dean
Received on Tuesday, 30 August 2011 19:41:32 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 30 August 2011 19:41:33 GMT