- From: Sebastian Zartner via GitHub <sysbot+gh@w3.org>
- Date: Fri, 22 Apr 2022 06:51:44 +0000
- To: public-css-archive@w3.org
> Oh, I guess my comment I wrote yesterday on the `color || stripes` bit didn't actually end up getting posted - we literally can't do `||` anyway, because it makes `border-color` ambiguous if it has anywhere between 2 and 7 entries. `border-color: red stripes(green, blue)` might be one value (cloned to all four sides) or two values (red top and bottom, stripes left and right). Given that "just color" is allowed today, the only way to do it at all is with `[ <1d-image>? <color> ]+` - that is, a _required_ color, with an optional 1d-image that _must_ precede it. You're right. I totally missed that ambiguity. Though I incidentally [brought up a solution for that earlier](https://github.com/w3c/csswg-drafts/pull/7029#issuecomment-1104969215) by requiring slashes between the values when `<1d-image>` is used. > But yeah, I don't understand the purpose of having both color and a 1d-image anyway. I understand the analogy you're drawing with background-color vs -image, but there's no use-case for this functionality in borders currently. More generally, we don't have the concept of layered borders like we have layered backgrounds. With the above said, I agree now to change it to `<color> | <1d-image>`. When use cases for layered borders arise, we can think about that again. Sebastian -- GitHub Notification of comment by SebastianZ Please view or discuss this issue at https://github.com/w3c/csswg-drafts/pull/7029#issuecomment-1106070791 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 22 April 2022 06:51:45 UTC