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

Re: [filters] computed value of the 'filter' property

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Tue, 23 Jul 2013 22:20:36 -0700
Message-ID: <CAAWBYDBAKAoQ6oBAnq-oBFMvb96NRE5JV3Keo3TH4hSJfs7ong@mail.gmail.com>
To: Cameron McCormack <cam@mcc.id.au>
Cc: "public-fx@w3.org" <public-fx@w3.org>
On Tue, Jul 23, 2013 at 5:36 PM, Cameron McCormack <cam@mcc.id.au> wrote:
> I don't think it's useful to have the computed value for the 'filter'
> property to keep distinguishing whether a filter primitive function's
> argument was a number or a percentage.  So can the 'Computed value' say
> something like:
>   as specified, but with numbers that indicate percentage values
>   computed to percentages
> or whatever is the appropriate way to word it.  I'm not sure whether
> computing these values to the percentage or the number or more common, so
> whichever way makes more sense.
> I'm assuming that numbers can be used to mean the same thing as percentages
> (with 0..1 meaning the same as 0%..100%), but this needs to be said
> explicitly.

Assuming that percentages are computed against something known ahead
of time (which I think they all are), yes, the computed value
shouldn't preserve the type.

Received on Wednesday, 24 July 2013 05:21:23 UTC

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