Re: [csswg-drafts] [css-gaps-1] Introduce `rule-visibility-items: auto` (#13477)

The CSS Working Group just discussed ``[css-gaps-1] Introduce `rule-visibility-items: auto` ``, and agreed to the following:

* `RESOLVED: Poll for whether Grid should default to 'between' or 'all'. Based on that, the initial value will be either 'between' or 'normal' (all for grid, between for multicol/flex)`

<details><summary>The full IRC log of that discussion</summary>
&lt;hoch> javierct: For rule visibility items we wanted to introduce 'auto'. rule-visibility-items allows authors to control where those rules are actually shown.<br>
&lt;hoch> javierct: The main issue is we have 3 different options: all, between, and around.<br>
&lt;hoch> javierct: Currently the default is set to 'all'<br>
&lt;oSamDavis> q+<br>
&lt;hoch> javierct: 'all' may cause backwards compatibility issue for multi-col. We'd still like it for grid, but would like to make a 'auto' to cover this.<br>
&lt;astearns> ack oSamDavis<br>
&lt;astearns> ack fantasai<br>
&lt;oSamDavis> q+<br>
&lt;astearns> ack oSamDavis<br>
&lt;kbabbitt> q+<br>
&lt;hoch> &lt;discussion of how the different keywords behaved><br>
&lt;hoch> fantasai: Kevin was wondering if the keyword should be 'normal' rather than 'auto'. I lean that direction. Matching gap.<br>
&lt;hoch> oSamDavis: It will be a rename 'auto' to 'normal', so 'normal' still resolves to one of the keywords?<br>
&lt;hoch> fantasai: yes<br>
&lt;astearns> ack kbabbitt<br>
&lt;fantasai> fantasai: Also curious what Rachel Andrew and Miriam think about the proposal.<br>
&lt;miriam> q+<br>
&lt;hoch> kbabbitt: In terms of the default behavior for grid, looking through the initial examples, there's examples for all 3 behaviors. The ones without empty cells were the first examples. Once we got into dev trials author cases came up for empty cells and between. I think 'all' is the most intuitive default and you can adjust as you want, even though<br>
&lt;hoch> it is inconsistent with the pre-existing behavior for multi-col.<br>
&lt;astearns> ack miriam<br>
&lt;hoch> miriam: 'between' is what I would have expected as the default in grid.<br>
&lt;hoch> kbabbitt: I would be open to making that change. Other opinions?<br>
&lt;hoch> astearns: I'm slightly in favor of consistency. Particularly since we have an existing behavior we have to support. Another benefit is we wouldn't have to use normal.<br>
&lt;hoch> astearns: Also in quite a lot of grid cases, the differences would be minimal.<br>
&lt;hoch> fantasai: flex would also default to 'all'?<br>
&lt;fantasai> s/all/between/<br>
&lt;hoch> kbabbitt: yes<br>
&lt;alisonmaher> q+<br>
&lt;astearns> ack alisonmaher<br>
&lt;hoch> alisonmaher: I lean towards having a different default for grid.<br>
&lt;astearns> ack fantasai<br>
&lt;hoch> fantasai: Maybe a straw poll on the name?<br>
&lt;hoch> fantasai: We can resolve here that if we're adding a keyword, it's 'normal'.<br>
&lt;fantasai> https://github.com/w3c/csswg-drafts/issues/11491#issuecomment-3711456023<br>
&lt;hoch> astearns: We should definitely resolve that the default mult-col behavior is between. The mechanism by which we get there is either a new keyword, or setting the default to 'between' for everything.<br>
&lt;fantasai> s|https://github.com/w3c/csswg-drafts/issues/11491#issuecomment-3711456023||<br>
&lt;fantasai> "Column rules are only drawn between two columns that both have content." -- https://www.w3.org/TR/css-multicol-1/#column-gaps-and-rules<br>
&lt;hoch> PROPOSED: The default behavior for rule-visibility-items is 'between' (for backwards compat), and then we will poll on how we get there.<br>
&lt;fantasai> PROPOSED: Poll for whether Grid should default to 'between' or 'all'. Based on that, the initial value will be either 'between' or 'normal' (all for grid, between for multicol/flex)<br>
&lt;fantasai> RESOLVED: Poll for whether Grid should default to 'between' or 'all'. Based on that, the initial value will be either 'between' or 'normal' (all for grid, between for multicol/flex)<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13477#issuecomment-4083463602 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 18 March 2026 15:30:14 UTC