- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Thu, 04 Mar 2021 00:45:46 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `Commas in color-mix()`, and agreed to the following: * `RESOLVED: Add back commas` <details><summary>The full IRC log of that discussion</summary> <Rossen_> Topic: Commas in color-mix()<br> <Rossen_> github: https://github.com/w3c/csswg-drafts/issues/6066<br> <fantasai> leaverou: Since we have rule that ? reptition should use commas but not other things<br> <fantasai> leaverou: we removed commas from color-mix because not a list<br> <fantasai> leaverou: but it doesn't read very nicely, and not clear which color the percentage belongs to<br> <fantasai> leaverou: so thinking to add the colors back<br> <Rossen_> q<br> <fantasai> leaverou: since we can't keep going back and forth about it, UAs are implementing<br> <fantasai> leaverou: Wanted to resolve this once and for all<br> <fantasai> leaverou: I also agree it's more readable with commas<br> <TabAtkins> q+ to agree<br> <una> q+<br> <fantasai> leaverou: I think it should have a comma to separate metadata from list of colors<br> <una> to also agree (we need commas)<br> <fantasai> leaverou: clarify whether about the first color or the function as a whole<br> <fantasai> leaverou: Seem to have consensus on adding them back<br> <fantasai> leaverou: Also, do we still have 'in' for color space?<br> <fantasai> leaverou: Seems like only have color space in the beginning<br> <Rossen_> ack TabAtkins<br> <Zakim> TabAtkins, you wanted to agree<br> <fantasai> TabAtkins: Agree with leaverou<br> <fantasai> TabAtkins: we're not attached to using commas everywhere like JS is<br> <fantasai> TabAtkins: only use it in some places<br> <fantasai> TabAtkins: It works reasonably here<br> <fantasai> TabAtkins: and helps with readability<br> <fantasai> TabAtkins: and we should also have the metadata in a single thought at the beginning, separated by comma<br> <fantasai> TabAtkins: consistent with gradients and shapes<br> <fantasai> TabAtkins: so +1 to what leaverou suggested<br> <Rossen_> ack una<br> <fantasai> una: I agree that commas are needed here<br> <fantasai> una: much like gradients<br> <miriam> +1 need commas<br> <fantasai> una: I also want to add, I don't think we need end keyword if we have this syntax<br> <leaverou> q+<br> <fantasai> una: I think we are reaching consensus in the issue, and +1 to proposal<br> <chris> s/end/in<br> <aja> fwiw, emilio landed on nightly, used commas, & % applied to 2nd color, "in srgb" at start or end. willing to change<br> <fantasai> leaverou: I would argue for 'in' keyword<br> <Rossen_> ack leaverou<br> <fantasai> leaverou: it reads better, and also lets us expand the syntax later to add more options<br> <fantasai> leaverou: So, makes it more readable and makes syntax less ambiguous, so argue to keep it<br> <fantasai> Rossen_: Seems like we have consensus around adding commas, any objections?<br> <chris> great, emilio already implemented what we are about to resolve <3<br> <fantasai> RESOLVED: Add back commas<br> <una> q+<br> <fantasai> Rossen_: Next one is do we want to have the 'in' keyword<br> <fantasai> una: I would like to object to it<br> <Rossen_> ack una<br> <leaverou> q+<br> <aja> chris, except for which color the percentage applies to<br> <TabAtkins> Also object, we don't use these sorts of intro keywords except absolutely necessary for disambiguation.<br> <fantasai> una: Reasoning, I don't think it's necessary and we don't have a construct of 'in' elsewhere in CSS, so introduces new concept not seen anywhere else and I don't think it adds clarity<br> <astearns> we have 'at' elsewhere<br> <fantasai> una: Don't want to add new syntax to CSS<br> <TabAtkins> Colorspace keywords are plenty clear and won't block our extensibility in the future.<br> <fantasai> Rossen_: OK, I suggest we open a separate issue for this<br> <TabAtkins> astearns, yeah, that's for disambiguation<br> <TabAtkins> because there are two positions<br> <Rossen_> ack leaverou<br> <fantasai> leaverou: Using prepositions for metadata in functions is common in gradients as well, which is where I got the inspiration. But agree with separate issue.<br> <fantasai> TabAtkins: I'm happy to argue that gradients are special<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6066#issuecomment-790193931 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 4 March 2021 00:45:48 UTC