Re: [fxtf-drafts] [filter-effects] blur() to take two parameters?

The Working Group just discussed `[filter-effects] blur() to take two parameters`, and agreed to the following resolutions:

* `RESOLVED: add a second param to blur() in L2 of filter-effects`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: [filter-effects] blur() to take two parameters<br>
&lt;dael> github:<br>
&lt;dael> krit: Currently takes one arguement, prop is to take 2 so you can blur in horiz and veritical with a different setting. I think this is good, but browsers don't impl. Move to level 2 or are browsers interested?<br>
&lt;dael> krit: I propose moving it to L2.<br>
&lt;dael> Chris: Agree. Since they all do 1 param it's better to move it and get impl interest first.<br>
&lt;dael> smfr: I agree. For webkit I'm happy to impl it in L2.<br>
&lt;dael> krit: Maybe we can also reolve to put it into L2?<br>
&lt;dael> astearns: Do we have a L2?<br>
&lt;dael> krit: Yes.<br>
&lt;dael> astearns: Great.<br>
&lt;dael> astearns: Obj to adding a second param to blur() in L2 of filter-effects?<br>
&lt;dael> Rossen_: What was the only impl?<br>
&lt;dael> krit: There is none. It's a proposal from a dev.<br>
&lt;dael> Rossen_: Okay.<br>
&lt;dael> dbaron: One thing to do is if it's in L2 to point out it's the new feature in a list that's elsewise the same.<br>
&lt;dael> krit: It's already a diff spec so yes.<br>
&lt;dael> RESOLVED: add a second param to blur() in L2 of filter-effects<br>

GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at using your GitHub account

Received on Wednesday, 24 January 2018 17:25:45 UTC