- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 09 Oct 2024 16:16:10 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed ``[css-overflow][css-contain][css-sizing] `overflow: auto` incompatible with size containment and container queries``, and agreed to the following: * `RESOLVED: Take 2nd option (reserve space as for scrollbar-gutter) and add a new value to scrollbar-gutter for inline-axis scrollbars (tbd)` * `ACTION: Florian to file a new issue on the new scrollbar-gutter value` <details><summary>The full IRC log of that discussion</summary> <fantasai> florian: A bit left on this issue. Already dealt with overflow and size containment<br> <fantasai> ... some instability in that, but solved already [quotes resolution]<br> <fantasai> ... in terms of 'overflow: scroll' we can apply the same principle, but first phase is with scrollbars and size accordingly<br> <fantasai> ... second phase where we don't need to add them, since laready there<br> <fantasai> ... solves first part of problem, but left with another one<br> <fantasai> ... which is question of instability of 'overflow: auto' and 'contain-intrinsic-size: auto"<br> <fantasai> ... if you put content in the element it adds scrollbars, then you freeze; if other way around, if freeze without knowing content then scrollbars don't take room and size differently, it's a problem<br> <fantasai> florian: in order to solve this I see 2 alternatives<br> <fantasai> florian: 1. contain-intrinsic-size:auto causes overflow:auto to compute to overflow:scroll<br> <fantasai> ... this removes instability by removing flexibility<br> <fantasai> florian: 2. reserve only scrollbar gutters; scrollbars don't get painted unless there's overflow but we reserve space for them<br> <fantasai> ... could explain as used value of scrollbar-gutter, but would need a new value for inline axis<br> <kizu> q+<br> <fantasai> oriol: I prefer the 2nd option, getting these gutters looks better than having scrollbars that don't scroll<br> <fantasai> oriol: thoug making overflow convert to scroll would be easier to implement<br> <astearns> ack kizu<br> <fantasai> oriol: fine with either option<br> <astearns> q+<br> <fantasai> kizu: Prefer the 2nd option. Especially I was surprised when scrollbar-gutter doesn't work in horizontal axis, would be useful<br> <fantasai> kizu: so support adding the new value and using it for this case<br> <fantasai> astearns: Asking for clarificaiton on 2nd option -- this could be explained in terms of scrollbar-gutter -- if we go with this option, are we absolutely adding a new value to scrollbar-gutter?<br> <astearns> ack astearns<br> <fantasai> florian: we have a choice. We could explain it conceptually without involving the property, or we can add a new value to the scrollbar-gutter property and use that value<br> <fantasai> s/use/invoke/<br> <fantasai> florian: but as mentioned, the new value could be useful in other cases<br> <fantasai> astearns: other opinions?<br> <fantasai> PROPOSED: Take 2nd option (reserve space as for scrollbar-gutter) and add a new value to scrollbar-gutter for inline-axis scrollbars<br> <fantasai> florian: need a name for it?<br> <fantasai> fantasai: existing values?<br> <fantasai> florian: auto | stable (applies to both start and end values)<br> <fantasai> florian: but we need a new value for inline and block<br> <florian> auto | stable && both-edges?<br> <fantasai> florian: currently scrollbar-gutter only applies to block-axis scrolling (scrollbars on the inline-axis edges of the box)<br> <fantasai> florian: could add new keywords 'inline' and 'block' and 'both' to combine with 'stable', defaulting to 'block'<br> <fantasai> florian: I'll open a new issue<br> <fantasai> RESOLVED: Take 2nd option (reserve space as for scrollbar-gutter) and add a new value to scrollbar-gutter for inline-axis scrollbars (tbd)<br> <florian> s/defaulting to 'block'/defaulting to 'inline'<br> <fantasai> ACTION: Florian to file a new issue on the new scrollbar-gutter value<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7875#issuecomment-2402760378 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 9 October 2024 16:16:10 UTC