Re: [css-houdini-drafts] [css-paint-api] Allow inputArguments define optional arguments

The Working Group just discussed `optional arguments in paint functions`, and agreed to the following:

* `RESOLVED: Deferred to L2`

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> Topic: optional arguments in paint functions<br>
&lt;TabAtkins> github: https://github.com/w3c/css-houdini-drafts/issues/763<br>
&lt;dbaron> github: https://github.com/w3c/css-houdini-drafts/issues/763<br>
&lt;fantasai> TabAtkins: Somebody wants optional arguments in paint functions<br>
&lt;fantasai> TabAtkins: It's a very reasonable request<br>
&lt;fantasai> TabAtkins: However, this falls under the more general issue of optional bits of syntax in custom properties<br>
&lt;fantasai> TabAtkins: which is currently not allowed because of issues around parsing ambiguity<br>
&lt;fantasai> TabAtkins: So we need disambiguation support first<br>
&lt;fantasai> florian: Is this a hard problem, or we need to sovle it but haven't yet?<br>
&lt;fantasai> TabAtkins: latter<br>
&lt;fantasai> TabAtkins: Definitely not impossible<br>
&lt;fantasai> TabAtkins: Support for more syntaxy things is slated for L2<br>
&lt;fantasai> fantasai: So proposal is close deferred to next level?<br>
&lt;fantasai> TabAtkins: That's what I would like<br>
&lt;fantasai> Rossen: Any other opinions?<br>
&lt;fantasai> RESOLVED: Deferred to L2<br>
&lt;fantasai> fantasai: Is there anything else is needed for the spec?<br>
&lt;fantasai> iank_: No<br>
&lt;fantasai> TabAtkins: TypedOM has changed how it handles image values<br>
&lt;fantasai> TabAtkins: which might affect this, but it's not affecting this spec<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/763#issuecomment-401653404 using your GitHub account

Received on Monday, 2 July 2018 02:13:11 UTC