- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Thu, 05 Jan 2023 00:32:03 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-contain-2] Clarify what happens with scrollbars on elements that 'skip their contents'`, and agreed to the following: * `RESOLVED: For elements in this situation we treat any overflow as ink overflow` <details><summary>The full IRC log of that discussion</summary> <dael> TabAtkins: I believe the right answer is fairly clear.<br> <dael> TabAtkins: The core issue is current spec text says if element skips contents they are not painted (as if visbility hidden). But if it's a scroller you still have to perform layout b/c need to know if trigges overflow. Seems like oversight b/c don't want to require layout<br> <dael> TabAtkins: Obvious case is make it assume no scrollbars are required. Some talk about saying "as if display:none" but that's not accurate either b/c would trigger lazy layout<br> <dael> TabAtkins: I think best is say skipped contents are treated as ink overflow so do not ever trigger scrollbars<br> <dael> astearns: Other side effects of ink overflow beyond creating scrollbars?<br> <dael> TabAtkins: No, only around how large the overflow rectangle is which is only to calc scrollbars<br> <dael> astearns: Prop: Any overflow is treated as ink overflow<br> <dael> smfr: Normally when think about ink overflow think about triggering paint invalidation. Never anything painted. So treating as ink overflow maybe not best?<br> <dael> TabAtkins: Since there's a scroller ink overflow will get trapped by the scroller<br> <dael> TabAtkins: Big thing is actual overflow area will be 0 essentially. Things are clipped but also invisible<br> <dael> smfr: Describe in terms of overflow:clip?<br> <dael> TabAtkins: I little reluctant to define in overflow b/c make sure do not stomp on existing overflow. Talking about in terms of ink allows us to avoid. If you think ther'es problems with ink we can look into it. At first blush want to stick with ink<br> <dael> astearns: Other concerns?<br> <dael> astearns: Prop: For elements in this situation we treat any overflow as ink overflow<br> <dael> astearns: Obj?<br> <dael> RESOLVED: For elements in this situation we treat any overflow as ink overflow<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5868#issuecomment-1371583199 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 5 January 2023 00:32:05 UTC