Re: [csswg-drafts] [css-borders-4] Add slashes between individual `border-color` values (#8026)

The CSS Working Group just discussed ``[css-borders-4] Add slashes between individual `border-color` values``, and agreed to the following:

* `RESOLVED: close no change`

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> SebastianZ: My point was that we're adding more features to the border-color shorthand<br>
&lt;fantasai> SebastianZ: to make the syntax more future proof, I suggested to change the syntax for when using features to add slashes between the different values for different sides<br>
&lt;fantasai> SebastianZ: or could be something else, but we already use slashes in border-image and grid-area<br>
&lt;fantasai> SebastianZ: we already added stripes() function, for example; this would make it clearer that they are different values<br>
&lt;emilio> fantasai: I don't think this is necessary, because stripes() is an image<br>
&lt;Rossen_> ack fantasai<br>
&lt;emilio> ... I think if we're going to make border-color more complicated we might want to pull it out into different longhands<br>
&lt;emilio> ... if we want to provide something like you'd do with backgrounds then we should have something else<br>
&lt;emilio> ... in most cases I don't anticipate that people will mix stripes() with other things<br>
&lt;oriol> +1 to elika<br>
&lt;fantasai> Rossen_: seems like good reason to not do this just yet<br>
&lt;fantasai> Rossen_: SebastianZ, anything to add?<br>
&lt;fantasai> Rossen_: otherwise we can resolve no change for now<br>
&lt;fantasai> SebastianZ: I think it's fine. My suggestion was to make it future-proof now rather than later<br>
&lt;fantasai> Rossen_: Proposed resolution is no change<br>
&lt;fantasai> Rossen_: we can return to it later if needed<br>
&lt;fantasai> RESOLVED: close no change<br>
</details>


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


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 9 August 2023 16:52:35 UTC