- From: CSS Meeting Bot via GitHub <noreply@w3.org>
- Date: Thu, 13 Nov 2025 05:19:44 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-gaps-1] Gap decorations next to empty grid areas`, and agreed to the following: * `RESOLVED: Add 'rule-visibility-items: all | around | between' (plus longhands)` <details><summary>The full IRC log of that discussion</summary> <astearns> zakim, open queue<br> <Zakim> ok, astearns, the speaker queue is open<br> <TabAtkins> kbabbitt: in August at f2f we talked a bit about this<br> <TabAtkins> kbabbitt: there are use-cases for not wanting decorations on all cells in grid<br> <TabAtkins> kbabbitt: [example] an unfilled grid area, don't want the deco crossing it<br> <TabAtkins> kbabbitt: [another example] don't want a deco between a filled area and an unfilled<br> <TabAtkins> kbabbitt: [another example] multicols, don't want lines between the empty columns at the end<br> <TabAtkins> kbabbitt: Elika suggested rule-visiblitity-items and rule-visiblity-self, I went with that<br> <TabAtkins> kbabbitt: working thru use-cases, realized just *-items is sufficient<br> <TabAtkins> kbabbitt: rv-items sets default over whole container for whether there's a deco in a gap between items when one or both sides is empty<br> <TabAtkins> kbabbitt: 'all' draws all decos. 'around' draws around items (between a filled and unfilled)<br> <TabAtkins> kbabbitt: 'between' only draws them between two filled (skips filled+unfilled)<br> <TabAtkins> kbabbitt: rv-self would let you set exceptions for specific items<br> <TabAtkins> kbabbitt: talking to Sam Davis, in our impl rv-self has some additional complexity<br> <TabAtkins> alisonmaher: currently gap-decos are set up on the container itself. we just track the segments and don't care about children.<br> <TabAtkins> alisonmaher: but if rv-self changed we'd have to rerun layout on the whole container to make it work<br> <TabAtkins> kbabbitt: so all the use-cases we have are satisfied with rv-items, either "around" or "between"<br> <TabAtkins> kbabbitt: [goes over the examples]<br> <astearns> q+ to ask about the first use case<br> <TabAtkins> kbabbitt: so my proposal for v1 is to just do rv-items: all | around | between;<br> <TabAtkins> kbabbitt: if we get feedback that we need it, we can add "none", and rv-items, if needed<br> <TabAtkins> astearns: I think it's fine to start simple and add complexity later<br> <TabAtkins> astearns: back in first use-case, you said this is solved with "around"<br> <TabAtkins> astearns: in this case, does author want deco to be entire width, or just over the right 2/3?<br> <astearns> ack astearns<br> <Zakim> astearns, you wanted to ask about the first use case<br> <TabAtkins> kbabbitt: that's a border actually<br> <astearns> ack fantasai<br> <TabAtkins> fantasai: this sounds good, looks like we have a path forward if we need it<br> <TabAtkins> fantasai: ftr should say "hidden" rather than "none", "hidden" suppresses in other contexts<br> <TabAtkins> kbabbitt: so proposed resolution is to introduce just rv-items, with "all | around | between" values<br> <kbabbitt> Proposed: Introduce column-rule-visibility-items: [ all | around | between ] and row-rule-visibility-items with same syntax, plus shorthand rule-visibility-items for both directions<br> <florian> +1<br> <miriam> excited to use this!<br> <TabAtkins> astearns: objections?<br> <TabAtkins> RESOLVED: Add 'rule-visibility-items: all | around | between' (plus longhands)<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12602#issuecomment-3525455371 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 05:19:45 UTC