Re: [csswg-drafts] [css-gaps-1] Bikeshedding names for ways to break gap decorations (#11491)

The CSS Working Group just discussed `[css-gaps-1] Bikeshedding names for ways to break gap decorations`, and agreed to the following:

* `RESOLVED: Close, no change.`

<details><summary>The full IRC log of that discussion</summary>
&lt;hoch> kbabbitt: This is about the different keywords for break behaviors. In the original spec we had none, spanning-item, and intersection.<br>
&lt;hoch> kbabbitt: To not break at all, break where an item is spanning 2 cells, and to break at every intersection<br>
&lt;hoch> kbabbitt: We've resolved to none, normal, and intersection.<br>
&lt;hoch> kbabbitt: I would like to confirm with the working group that these are acceptable terms. No new suggestions.<br>
&lt;astearns> ack fantasai<br>
&lt;hoch> fantasai: Flipping through the thread there's an interesting idea about inverting the rule and flipping the name of the property. Making it rule-join instead of rule-break. Making the values maybe all, none, and<br>
&lt;fantasai> s/and/and skip-item/<br>
&lt;fantasai> scribe+<br>
&lt;fantasai> kbabbitt: We discussed internally, but thought that if in the future we introduce more controls for more things, it would be easier to add values to a break property (more things to break on ) vs trying to incorporate that into a join property.<br>
&lt;kbabbitt> kbabbitt: for example controlling T intersections versus cross intersections separately<br>
&lt;hoch> astearns: Skimming through the thread I'm a little concerned about the non-descript nature of 'normal', but I don't have a better idea.<br>
&lt;oSamDavis> q+<br>
&lt;hoch> kbabbitt: normal does want an author would hand-wavy expect.<br>
&lt;hoch> kbabbitt: Was there a special behavior for that in flex?<br>
&lt;hoch> javierct: no. normal ends up behaving as intersection.<br>
&lt;hoch> kbabbitt: intersection in the cross direction, none in the other direction<br>
&lt;hoch> javierct: yes, we renamed to normal because of that dual meaning<br>
&lt;astearns> ack oSamDavis<br>
&lt;hoch> PROPOSED: Close this, no change<br>
&lt;hoch> RESOLVED: Close, no change.<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11491#issuecomment-4083349945 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:40:11 UTC