[csswg-drafts] [css-overflow-4] overflow into the gutter (#5253)

frivoal has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-overflow-4] overflow into the gutter ==
If an element has a [scrollbar gutter](https://drafts.csswg.org/css-overflow-4/#scrollbar-gutter-property) on its inline end side, and some content of that element (or its children) that would qualify as scrollable overflow extends into the gutter (but not beyond), do we consider that:
1. The gutter is kind of an extension of the padding, and overflowing into the padding in the inline axis doesn't cause a need for scrollbars, so this doesn't either
2. the gutter is after the padding, and normally things extending outside a box’s padding edge get a scrolling mechanism (per https://drafts.csswg.org/css-overflow-3/#scrollable), so if you overflow into the right gutter, you should get a horizontal scrollbar to be able to scroll to that content
3. we should do 1 if the scrollbars are overlay, and 2 if the scrollbars are classic, because that's what you need to be able to see the content
4. something else?


A strict interpretation of 1 is wouldn't be web compatible: a the very least we need a scrollbar to access content that goes into a gutter in which there is a visible classic scrollbar, since that's the legacy behavior, and since otherwise, that content would be unreachable.

For stability's sake, I think we should extend that to `stable` gutters with classic scrollbars even when the scrollbar is not visible (i.e. `overflow:auto` and no overflowing content in the block axis). Same thing for `always` gutters, since in the case of classic scrollbars, they're the same as `stable` ones. So that would mean doing 3.

We could also do 2, but that doesn't seem useful / necessary.




Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5253 using your GitHub account

Received on Tuesday, 23 June 2020 09:01:30 UTC