- From: Oriol Brufau via GitHub <noreply@w3.org>
- Date: Sun, 01 Feb 2026 14:44:51 +0000
- To: public-css-archive@w3.org
@bradkemper > I hope we can also go the other direction and have border-offset. Outlines don't affect layout, so offseting them is no big deal. For borders it's not clear if the offset would affect the size of the border box during layout? But file a new issue if you want to pursue this. > For outline-offset and border-offset, there are some interesting effects that can be accomplished by allowing them to be listified too That seems too much complication for no much gain. Authors can just insert a transparent border stripe (except if they wanted a negative offset to make stripes overlap, but that seems very corner-casey) > Adding a second border shouldn't change the first border Note going outwards means that adding a second border can change the shape of the first one if there is a `border-radius`, because it applies to the outer one. > The decision about `border-style: none` feels weird and inconsistent to me. We have plenty of precedents of lists where a `none` value can't be an item of a list, and instead just represents an empty list. So I don't think it's weird. Not sure why you would use `border-style: solid, solid, none` instead of removing the last length from `border-width`. Still, if authors ask for it, it can be discussed in the future to allow `none` in lists. Allowing `hidden` in a way that makes sense seems trickier. -- GitHub Notification of comment by Loirooriol Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13044#issuecomment-3831146326 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 1 February 2026 14:44:51 UTC