Re: [csswg-drafts] [css-borders] Allow multiple borders by listifying them (#13044)

I've changed the title of the issue to clarify what the general proposal is about.

We're at a point where it's hard to follow the different suggested approaches for how to define different syntaxes. @LeaVerou did a great job at carving out @jsnkuhn's initial proposal for [listifying the `border-*` properties](https://github.com/w3c/csswg-drafts/issues/13044#issuecomment-3474612084).

As @Loirooriol [wrote earlier](https://github.com/w3c/csswg-drafts/issues/13044#issuecomment-3693400117), we should reach consensus what are the main use cases to cover by allowing multiple borders.

Based on that, we should decide on the general approach to this. At the moment, I believe we have two main ones:

1. **Listifying the `border-*` properties (the proposal here)**
2. **A function for one of the `border-*` properties (i.e. keep the currently defined `stripes()` or replace it by a similar functional solution)**

Like others, I'd classify @Crissov's [idea of introducing an at-rule](https://github.com/w3c/csswg-drafts/issues/13044#issuecomment-3686993217) as a possible solution for some more advanced border styling, which is great but goes far beyond the main use cases.

So let's bring this to the agenda and see if we can get an agreement on the main use cases we want to cover and the general direction we want take.

Once we have an agreement on those points, we can further discuss the details and try to get resolutions on those.

Sebastian

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


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

Received on Friday, 2 January 2026 10:06:06 UTC