- From: Calvin Walton via GitHub <noreply@w3.org>
- Date: Sun, 28 Dec 2025 18:35:35 +0000
- To: public-css-archive@w3.org
Keep in mind that at some point, it's a responsibility of web developers to actually read the specs/documentation, try things out themselves, and internalize knowledge (or at least know where to find reference material) on how to use the various CSS properties. Seeing
```css
border: solid #000 1px, dashed red 3px, solid #000 1px;
```
and saying "that defines a border on three sides" is, to me, less intuitive than saying "that defines three borders" given how existing list properties work, especially `background-image`. The current `border` shorthand doesn't allow setting any per-side properties, and commas aren't used in any of the current border properties, so this is something new and different. And if you see this new syntax when poking at a site in web inspector, you will see the CSS live right beside the result - that should make it quite clear what's going on.
Anyone who sees the new syntax will probably want to look it up or try it out themselves to see how it works and what it can do, and they only really need to figure out two new rules that work on all of the regular border properties (i.e. excluding rounded corners and border images) on top of what they already know about borders. My preference is "commas separate multiple borders in order from inside to outside; number of borders is determined by `border-style`". I personally think this is a lot simpler to learn than an entirely new "1d image" concept (plus setting the value of a `color` property to be an image bugs me).
Doing some typesetting in specs and documentation to put properties for different borders on separate lines, like:
```css
border-width: 1px 2px,
4px 3px 2px 1px;
```
would go a long way towards making it clear how the properties work.
--
GitHub Notification of comment by kepstin
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13044#issuecomment-3694949151 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 28 December 2025 18:35:36 UTC