Re: [css-houdini-drafts] [css-properties-values-api] Allow comma-separated lists in registered properties

The Working Group just discussed `Allow comma-separated lists in registered properties`, and agreed to the following:

* `RESOLVED: Add # to Properties and Values grammar syntax.`

<details><summary>The full IRC log of that discussion</summary>
&lt;heycam> Topic: Allow comma-separated lists in registered properties<br>
&lt;heycam> github: https://github.com/w3c/css-houdini-drafts/issues/768<br>
&lt;heycam> TabAtkins: the request is from Sam Richard, pointing out a lot of properties are comma separated lists<br>
&lt;heycam> ... right now the grammar for custom props allows just values separated by spaces, no repetition<br>
&lt;heycam> ... I think it's reasonable to allow top level comma repetition<br>
&lt;heycam> ... would be happy to put this into the syntax spec<br>
&lt;heycam> fantasai: do we have the ability to repeat without commas?<br>
&lt;heycam> TabAtkins: no<br>
&lt;heycam> ... not currently<br>
&lt;heycam> fantasai: then I think those two should be added together, so people aren't forced to add commas just because they want repetition even when it would be innappropriate to use commas<br>
&lt;heycam> TabAtkins: that's probably reasonable<br>
&lt;heycam> ... the grammar work to allow commas like a CSS grammar is similar to the work for space repetition<br>
&lt;heycam> ... will have to add a way to make that unambiguous, require the repeating part at the end or something<br>
&lt;heycam> birtles: we also need to specify how to animate the lists, if they're mismatched lengths<br>
&lt;heycam> fantasai: currently do you have multi valued properties at all?<br>
&lt;heycam> TabAtkins: yes<br>
&lt;dbaron> (animation types are in https://drafts.csswg.org/css-transitions/#interpolated-types )<br>
&lt;heycam> TabAtkins: right now, you can do space separated repetition, but only of the entire thing<br>
&lt;heycam> fantasai: so you would add comma repetition of the entire thing<br>
&lt;heycam> TabAtkins: we don't have brackets yet<br>
&lt;heycam> fantasai: you just need a hash<br>
&lt;heycam> TabAtkins: that would only allow &lt;length>#, not [&lt;length> | &lt;percentage>]#<br>
&lt;heycam> ... can only repeat a single term<br>
&lt;heycam> fantasai: that's a limitation currently for space separated avlues<br>
&lt;heycam> TabAtkins: yes<br>
&lt;heycam> ... at minimum, just adding that would work out ok though<br>
&lt;heycam> ... the big issue is to define what the default list animation behavior is, and possibly allow a way to change which behavior you want there<br>
&lt;heycam> fantasai: don't you have that question for &lt;length>+ as well?<br>
&lt;heycam> TabAtkins: I'm not sure how that one animates<br>
&lt;heycam> ... I think they just have to match in length right now<br>
&lt;heycam> dbaron: so that's the "simple list" definition in Transitions<br>
&lt;heycam> ... the least common denominator thing is a generic thing<br>
&lt;heycam> ... there are other things like for shadows with specific behavior<br>
&lt;heycam> ... filters should have something similar<br>
&lt;heycam> TabAtkins: I think it does<br>
&lt;fantasai> s/generic thing/generic thing/that repeats the list/<br>
&lt;fantasai> s/generic thing/generic thing that repeats the list/<br>
&lt;heycam> frremy: I think we should try to find an easy way to handle animations now in L1, then look at more complicated animations in L2<br>
&lt;fantasai> s/specific specific values used to fill missing spots/<br>
&lt;fantasai> s/specific values/specific values used to fill missing spots/<br>
&lt;heycam> ... I feel like we should have an easy answer in L1, try to find use cases for more something complex<br>
&lt;fantasai> s/specific/specific values used to fill missing spots/<br>
&lt;heycam> TabAtkins: so we can use simplie list behavior now, then figure out what we need for later<br>
&lt;heycam> TabAtkins: objections to adding the # multiplier to L1 grammar?<br>
&lt;heycam> dbaron: adding both the # and +?<br>
&lt;heycam> TabAtkins: + is already in the grammar<br>
&lt;heycam> Rossen: any objections?<br>
&lt;heycam> fantasai: so add # with the same definition and abilities as +<br>
&lt;heycam> RESOLVED: Add # to Properties and Values grammar syntax.<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/768#issuecomment-401641773 using your GitHub account

Received on Sunday, 1 July 2018 23:53:21 UTC