Re: [csswg-drafts] [css-borders] allow multiple borders (#13044)

![example image from the specification](https://drafts.csswg.org/css-borders/images/borderstyles.png)

It would be nice to be able to introduce common, mandatory definitions for the [`<line-style>`](https://drafts.csswg.org/css-borders/#typedef-line-style) keywords, but that is hardly different for listified `border-color` and a functional stripe notation. As Tab already noted, `dotted` and `dashed` can be represented by neither, `double` would be something like `currentcolor transparent currentcolor` and for the rest, two sides would always be equal: left = top, right = bottom (usually absolute not logical methinks); they would differ in which of the pairs is darkened and which lightened from the specified or inherited border color, which are all solid for `inset`/`outset` and collapsed `ridge`/`groove`, which otherwise are composed of simple outer+inner two-color stripes. 

Regarding the requested more complex use cases, I _wanted_ to say “national flag colors”, particularly around respective holidays, but researching that a bit, multicolored stripes would often not be enough even if the local flag was a classic tricolor. In the US, for instance, the stars are often featured somehow. Also, many people seem to like a more ribbon-like representation, even if plain borders do occur, e.g. in red, white and blue commonly in US, UK, France and Thailand despite them having very different flag designs. 🇺🇸🇬🇧🇫🇷🇹🇭

My conclusion, left for another issue to be created, therefore is that `border-style` should support (automatically repeated) [basic shapes](https://drafts.csswg.org/css-shapes-1/#basic-shape-functions), where the default reference box might be a square `border-width`. (I also have a half-baked alternative in mind, where shakes become usable within `border-image`, or generally `<image>`.)

-- 
GitHub Notification of comment by Crissov
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13044#issuecomment-3491754050 using your GitHub account


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

Received on Wednesday, 5 November 2025 15:06:32 UTC