Re: [csswg-drafts] [css-overflow] Understanding the shape of the clip with scrollbar-gutters (#13407)

The CSS Working Group just discussed `[css-overflow] Understanding the shape of the clip with scrollbar-gutters`, and agreed to the following:

* `RESOLVED: update scrollbar-gutters feature to include the View Transitions use-case`

<details><summary>The full IRC log of that discussion</summary>
&lt;ydaniv> vmpstr: looking at this since in VTs we have pseudo tree, and one element is called v-t-group-children which is meant to hold the participating elements<br>
&lt;ydaniv> ... this element shuld have a shape, and if it has a clipping it should ...<br>
&lt;ydaniv> ... for now we're coping border-shape and border-radius and it sets the clip<br>
&lt;ydaniv> ... in the presence of classic scrollbars the clip is wrong<br>
&lt;ydaniv> ...  the scrollbar-gutters should fix this, but it has some limitations<br>
&lt;ydaniv> ... 3 things that need to change for us to be able to use scrollbar-gutters in VTs<br>
&lt;ydaniv> ... 1. it requires a scroller, so only has an effect if hidden/scroll/auto<br>
&lt;ydaniv> ... would be nice if it didn't require that, so that I could reserve place anyway<br>
&lt;florian> q+<br>
&lt;ydaniv> ... 2. scrollbar-gutter doesn't allow us to specify for block side of the box, only the inline<br>
&lt;astearns> q+<br>
&lt;ydaniv> ... from impl. perspective shouldn't be a problem<br>
&lt;ydaniv> ... 3. probably just spec text issue, classic scrollbars put the gutter on the inner side of the scrollbars<br>
&lt;ydaniv> ... in practice we see in WK a rectangular shape, FF shows ...<br>
&lt;astearns> ack florian<br>
&lt;ydaniv> florian: why we don't have on the block side, there was no difficulty, but the use-case we had only cared about the inline side<br>
&lt;ydaniv> ... having a scrollbar-gutter or not is not a problem, wanted to keep the scope limited, if there's a good reason to expand should not be a probelm<br>
&lt;flackr> qq+<br>
&lt;astearns> ack astearns<br>
&lt;astearns> ack flackr<br>
&lt;Zakim> flackr, you wanted to react to florian<br>
&lt;ydaniv> astearns: my impression is that scrollbar-gutters is about space, not so much about the shape of the element, so wonder whether it's appropriate to look at this when looking at the shape<br>
&lt;ydaniv> flackr: my understaing of SGs is to not have a chnage if scollers show or not, so in case of shape should probably have the same behavior<br>
&lt;ydaniv> vmpstr: is there any thoughts on removing certain reservation on overflow values for rendering a gutter?<br>
&lt;ydaniv> ... current text I read requires these values<br>
&lt;ydaniv> florian: other values have been considered, it is in appendix B - the 4th value<br>
&lt;ydaniv> ... so far it's just a proposal, we can push forward separately<br>
&lt;florian> https://www.w3.org/TR/css-overflow-4/#valdef-scrollbar-gutter-force<br>
&lt;ydaniv> ... if you need anything else we should investigate<br>
&lt;ydaniv> vmpstr: one thing I need is the inline side, and the value restriction is the 2nd<br>
&lt;ydaniv> astearns: so next step would be to try to update the design of SGs so that it would setisfy the use-case of VTs<br>
&lt;ydaniv> ... is that something you would volunteer to work on?<br>
&lt;ydaniv> vmpstr: can do (:<br>
&lt;ydaniv> ... if florian can review?<br>
&lt;ydaniv> florian: sure<br>
&lt;ydaniv> astearns: any objections on doing this?<br>
&lt;ydaniv> PROPOSED RESOLUTION: update scrollbar-gutters feature to include the View Transitions feature<br>
&lt;ydaniv> RESOLVED: update scrollbar-gutters feature to include the View Transitions use-case<br>
</details>


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


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

Received on Wednesday, 25 February 2026 16:36:15 UTC