Re: [csswg-drafts] [css-gaps-1] Asymmetric start and end offsets (#12603)

The CSS Working Group just discussed `[css-gaps-1] Asymmetric start and end offsets`, and agreed to the following:

* `RESOLVED: rule-outset: <inner-start> <inner-end>? [/ <outer-start> <outer-end>?]?`

<details><summary>The full IRC log of that discussion</summary>
&lt;emilio> fantasai: inner / outer should take too value, but shorthand will take four values<br>
&lt;kbabbitt> rule-outset: &lt;inner-start> &lt;inner-end> / &lt;outer-start> &lt;outer-end><br>
&lt;emilio> SebastianZ: three right? outer only one?<br>
&lt;kbabbitt> rule-outset: &lt;inner-start> &lt;inner-end> [/ &lt;outer-start> &lt;outer-end>]<br>
&lt;alisonmaher> q+<br>
&lt;emilio> fantasai: it's reasonable to extend differently<br>
&lt;astearns> ack alisonmaher<br>
&lt;emilio> ... we should do it in both axes<br>
&lt;emilio> alisonmaher: going back to this impacting layout... gap decorations are painted at the container level, so item level control we're proposing...<br>
&lt;emilio> fantasai: we're not doing item-level control here, that's start v end<br>
&lt;emilio> ... for the other issue the container is still painting the decorations, just consulting the items<br>
&lt;emilio> emilio: just like tables :')<br>
&lt;SebastianZ> q+<br>
&lt;emilio> kbabbitt: I propose single values for all, slash separates inside vs. outside, space start and end<br>
&lt;astearns> ack SebastianZ<br>
&lt;emilio> SebastianZ: wondering whether that targets the intersections between...<br>
&lt;emilio> ... we should have a value for ?? both<br>
&lt;emilio> ... to meet both?<br>
&lt;emilio> fantasai: 50%?<br>
&lt;emilio> SebastianZ: I think so<br>
&lt;emilio> fantasai: we could add a keyword if we want<br>
&lt;fantasai> emilio: for the 50% thing, you need to be careful with transparency<br>
&lt;fantasai> emilio: don't paint two borders in the same place<br>
&lt;fantasai> emilio: when they meet, you either combine the borders into one and paint with that color, or paint both<br>
&lt;fantasai> emilio: are there use cases for these?<br>
&lt;emilio> fantasai: I think what you want is that as long as they overlap you do one line<br>
&lt;astearns> proposed shorthand syntax: rule-outset: &lt;inner-start> &lt;inner-end> [/ &lt;outer-start> &lt;outer-end>]<br>
&lt;emilio> emilio: but that's tricky right? that depends on DPI<br>
&lt;emilio> emilio: some questionmarks missing I think?<br>
&lt;emilio> ... but yeah that seems fine<br>
&lt;fantasai> PROPOSED: rule-outset: &lt;inner-start> &lt;inner-end>? [/ &lt;outer-start> &lt;outer-end>?]?<br>
&lt;kbabbitt> rule-outset: &lt;inner-start> &lt;inner-end>? [/ &lt;outer-start> &lt;outer-end>?]?<br>
&lt;fantasai> RESOLVED: rule-outset: &lt;inner-start> &lt;inner-end>? [/ &lt;outer-start> &lt;outer-end>?]?<br>
</details>


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


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

Received on Wednesday, 20 August 2025 14:17:01 UTC