Re: Proposal: feHSL element (was Re: [filter-effects] hue-rotate() and saturate() filters)

Hi Dean and Chris,

I would like to clarify if you are both on the same side.

So you both agree that we should have a new feHSL element?

You both agree that his primitive should operate in HSL regardless of the specified value of the 'color-interpolation-filters' property?

And you both agree that you do not want to fix hue-rotate() but create a new shorthand function for this new operation?

For me it sounds like you mean different things. While you Chris mean the filter primitive element, Dean is talking about the filter function. I might be wrong though.

Greetings.
Dirk


On Oct 18, 2013, at 5:01 PM, Chris Lilley <chris@w3.org> wrote:

> Hello Dean,
> 
> Thursday, October 17, 2013, 11:10:41 PM, you wrote:
> 
> 
>> On 17 Oct 2013, at 8:59 am, Chris Lilley <chris@w3.org> wrote:
> 
>>> Hello Rik,
>>> 
>>> Wednesday, October 16, 2013, 10:59:11 PM, you wrote:
>>> 
>>>> It seems that this should work and be lightweight.
>>> 
>>> Thanks.
>>> 
>>>> I'm unsure if we should add a new filter element or just update the CSS shorthands.
>>> 
>>> I suggest both; update the CSS shorthands to point to this, and add
>>> the filter so that longhand (user constructed) filters can use it as
>>> one component.
> 
>> As sucky as the results of hue-rotate currently are, the fact that it
>> is described as a matrix operation means we can implement it easily
>> with hardware acceleration on less powerful platforms.
> 
> Agreed.
> 
> Also, there will be content where the author tweaked until
> they got the result they wanted; if we modify the definition in place
> it will break that content.
> 
>> For that reason I’d be hesitant to change the definition to something
>> that would require us to regress performance. So I guess I’m voting
>> for a new operation and keyword.
> 
> Yes.
> 
> 
> 
> 
> -- 
> Best regards,
> Chris                            mailto:chris@w3.org
>

Received on Friday, 18 October 2013 16:25:53 UTC