- From: Oriol Brufau via GitHub <sysbot+gh@w3.org>
- Date: Thu, 17 Jan 2019 22:15:43 +0000
- To: public-css-archive@w3.org
> I don't think `border` is the correct analog here. `border-horizontal/vertical` would be `border` is still a great analog. The difference is that it maps to 4 sides instead of 2, but the number is not that important. What matters is that they are shorthands for multiple sides, and the property for each side is also a multi-valued shorthand. In fact, if this is added to `border-block` and`border-inline`, probably I would also want it in `border` for consistency. > It needs to be some other character like `"/"`. This way the separation is more obvious. However, I would expect ```css border-inline: solid orange 5px / dotted; ``` to be treated as ```css border-inline: solid orange 5px / dotted currentColor medium; ``` instead of as ```css border-inline: solid orange 5px / dotted orange 5px; ``` which is what fantasai proposed and seemed more useful to me, because I rarely want the initial border values. Not sure which behavior you are proposing. > I'd like the spec to make a note I agree with this, in fact [`border`](https://drafts.csswg.org/css-backgrounds-3/#propdef-border) already has this note: > Unlike the shorthand `margin` and `padding` properties, the `border` property cannot set different values on the four borders. To do so, one or more of the other border properties must be used. -- GitHub Notification of comment by Loirooriol Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3519#issuecomment-455352152 using your GitHub account
Received on Thursday, 17 January 2019 22:15:44 UTC