- From: CSS Meeting Bot via GitHub <noreply@w3.org>
- Date: Thu, 13 Nov 2025 06:46:00 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed ``[css-backgrounds] allow optional forward slash in `border-*-radius` long hands``, and agreed to the following: * `RESOLVED: Allow forward slash in these properties.` <details><summary>The full IRC log of that discussion</summary> <TabAtkins> fantasai: someone outside the WG wanted to propose we allow / separating the x and y values of border-radius, also in the longhands<br> <TabAtkins> fantasai: right now borde-rradius takes 1-4 values, a slash, then 1-4 values. x/y<br> <TabAtkins> fantasai: but in the longhands it's just two values, space-separated<br> <oriol> q+<br> <TabAtkins> fantasai: they thought it was confusing, wanted to put / in the longhands as well<br> <fantasai> oriol: This would have been good from the beginning, but now that we're using spaces, but at this point<br> <fantasai> oriol: It might add confusion, if an author sees the two options, wouldn't be obvious that they mean the same thing<br> <lea> q+<br> <kbabbitt> q+<br> <fantasai> oriol: I'm not strongly opposed, but lean against<br> <astearns> ack oriol<br> <astearns> ack lea<br> <fantasai> lea: Seems reasonable to me. I could argue that we should have done it originally, it is weird to be different.<br> <fantasai> lea: I'm in favor of this change.<br> <astearns> ack kbabbitt<br> <fantasai> kbabbitt: I empathize with the author<br> <fantasai> kbabbitt: but there are other places where we do this, concerned about lack of ocnsistency<br> <astearns> ack fantasai<br> <TabAtkins> fantasai: in colors we introduced an alternate punctuation<br> <ChrisL> rssagent, draft minutes<br> <TabAtkins> fantasai: it's not common to set x/y radius independently in the longhands. it happens, but you're usually using the shorthand, or setting both to same value<br> <TabAtkins> fantasai: wrt other places where we use slash, mostly it's places where wer'e combining two longhands and need the / to separate two numbers<br> <TabAtkins> fantasai: don't think we have any other example of where a / is used in the shorthand to separate two values, but those same two values in the longhand aren't slash-separated<br> <TabAtkins> fantasai: like in background-position, the / separates sizing from offsets. but in the longhands they're separate things<br> <TabAtkins> fantasai: so I think the consistency argument here is an overall win for authors.<br> <fantasai> astearns: Slight concern that we can resolve to make this change but never gets implemented.<br> <fantasai> astearns: doesn't seem high priority for anyone<br> <fantasai> astearns: but I'm hearing some slightly more sentiment towards making the change than opposition<br> <fantasai> astearns: Shall we resolve to change the spec?<br> <fantasai> oriol: To clarify, we alias at parse time?<br> <fantasai> astearns: And continue return without slash for comat<br> <fantasai> fantasai: yes<br> <fantasai> PROPOSED: Allow forward slash in these properties.<br> <fantasai> RESOLVED: Allow forward slash in these properties.<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12861#issuecomment-3525806102 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 13 November 2025 06:46:01 UTC