- From: CSS Meeting Bot via GitHub <noreply@w3.org>
- Date: Wed, 18 Feb 2026 17:59:04 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed ``[css-borders-4]: `border-shape` order of shapes in the two-shape variant``, and agreed to the following: * `RESOLVED: Close no change, don't mind the inconsistency with listified borders` <details><summary>The full IRC log of that discussion</summary> <emilio> noamr: `border-shape` has two variants, one-shape (stroke) and two-shape (filled)<br> <emilio> ... inner one is the overflow-clip<br> <emilio> ... currently order is outer then inner<br> <astearns> q+<br> <emilio> ... are we going with this or is it confusing?<br> <emilio> ... raised because of the multiple-borders discussion<br> <astearns> q-<br> <emilio> ... after running polls I think they came inconclussive<br> <emilio> ... my current suggestion is close no change (keep outer then inner)<br> <emilio> ... with future option to make border-shape a shorthand that has two values<br> <emilio> q+<br> <astearns> border list issue: https://github.com/w3c/csswg-drafts/issues/13044<br> <astearns> ack emilio<br> <smfr> q+<br> <emilio> emilio: were the polls about border-width unconclusive? or only the border-shape<br> <astearns> ack smfr<br> <emilio> noamr: border-shape were unconclusive, border-width were more conclusive towards inside-out<br> <emilio> emilio: any reason not to be consistent if border-shape is 50/50?<br> <emilio> smfr: my thinking about why border-shape was outside-in?<br> <emilio> ... I don't think it of outside-in<br> <emilio> ... the first one is the fundamental shape of the element<br> <astearns> q+<br> <emilio> ... the second one is an embellishment<br> <noamr> +1<br> <emilio> ... if you only supply one it's the outer one<br> <fantasai> +1<br> <emilio> ... makes more sense to me<br> <astearns> ack astearns<br> <emilio> astearns: if that was natural wouldn't it be more natural for the borders thing?<br> <emilio> smfr: don't think so, extra ones pile outside because they're extra for me<br> <emilio> q+<br> <astearns> ack emilio<br> <noamr> Scribe+<br> <emilio> astearns: I think it'd be slightly nicer if they were consistent but I don't worry too much about this<br> <lwarlow> I think inconsistent is fine fwiw, these will be learned orders anyway. The docs will make it clear.<br> <noamr> emilio: I buy the argument from Simon. it will be good for the spec to speak about it in those terms<br> <noamr> emilio: rather than inner/outer<br> <fantasai> Yeah, I'm not convinced about a shorthand making sense here.<br> <noamr> emilio: having an inner/embelishment without an outer probably doesn't make sense so probably also not a shorthand<br> <emilio> PROPOSED: Close no change, don't mind the inconsistency with listified borders<br> <lea> (Agree with the resolution)<br> <emilio> RESOLVED: Close no change, don't mind the inconsistency with listified borders<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13308#issuecomment-3922319623 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 18 February 2026 17:59:05 UTC