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

On Jul 24, 2013, at 7:20 AM, Tab Atkins Jr. <> wrote:

> On Tue, Jul 23, 2013 at 5:36 PM, Cameron McCormack <> 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.

I disagree on this. It would be inconsistent with other usage of unit values in other properties. We should preserve the unit. Furthermore, Cam is talking about some filter functions. There are others that take length values and degrees. We certainly want to keep units here. If we do not have the percentage value on the filter functions mentioned by Cam, the computed property values would look inconsistent in itself.


> ~TJ

Received on Wednesday, 24 July 2013 05:57:25 UTC