Re: [csswg-drafts] [css-conditional-5] scroll-state(overflowing) is confusing because it ignores clipped overflowing content (#11182)

The CSS Working Group just discussed `[css-conditional-5] scroll-state(overflowing) is confusing because it ignores clipped overflowing content`, and agreed to the following:

* `RESOLVED: Rename "overflowing" to "scrollable"`

<details><summary>The full IRC log of that discussion</summary>
&lt;TabAtkins> futhark: there's scroll-state(overflowing) which is true if there is content overflowing in that axis<br>
&lt;TabAtkins> futhark: elika points out that there may be overflowing content that can't be scrolled to. she recommends renaming the value to 'scrollable'<br>
&lt;miriam> +1 scrollable<br>
&lt;argyle> +1 scrollable<br>
&lt;TabAtkins> futhark: I agree. Suggest we use this name unless people have other suggestions.<br>
&lt;TabAtkins> +1<br>
&lt;TabAtkins> fantasai: think this is a good summary<br>
&lt;kbabbitt> +1 scrollable<br>
&lt;fantasai> s/content overflowing/content overflowing and scrollable to/<br>
&lt;smfr> q+<br>
&lt;kizu> q+<br>
&lt;TabAtkins> astearns: proposed resolution is to rename 'overflowing' to 'scrollable'<br>
&lt;astearns> ack smfr<br>
&lt;TabAtkins> smfr: is this only user-scrollable overflow? or also overflow:hidden?<br>
&lt;kizu> q- same question<br>
&lt;dbaron> s/hidden/hidden, which can be programmatically scrolled/<br>
&lt;TabAtkins> futhark: overflowing content that can be scrolled to *with the UI*<br>
&lt;astearns> ack kizu<br>
&lt;TabAtkins> kizu: yeah same, in a lot of aspects 'hidden' behaves as other scrollable values like 'auto' or 'scroll'<br>
&lt;emilio> I think it should apply to hidden fwiw<br>
&lt;astearns> ack fantasai<br>
&lt;TabAtkins> kizu: i think there are situations authors might want to know if there is clipped content that could be script-scrolled to<br>
&lt;emilio> (but not clip=<br>
&lt;TabAtkins> fantasai: maybe a separate issue, i think i agree it should apply to hidden as well<br>
&lt;TabAtkins> fantasai: the author knows if it's hidden or not, that's not an interesting part of the query<br>
&lt;TabAtkins> fantasai: but i think that should be another issue<br>
&lt;TabAtkins> +1 to fantasai<br>
&lt;TabAtkins> astearns: are you okay punting to a separate issue?<br>
&lt;TabAtkins> kizu: yup<br>
&lt;TabAtkins> astearns: so proposed resolution, rename "overflowing" to "scrollable". objections?<br>
&lt;fantasai> s/that's not an interesting part of the query/this becomes an uninteresting query for hidden elements if it doesn't work on hidden<br>
&lt;emilio> +1 on the rename<br>
&lt;TabAtkins> RESOLVED: Rename "overflowing" to "scrollable"<br>
&lt;emilio> +1 to make it work on hidden too :)<br>
&lt;TabAtkins> astearns: I'll get the other two async resolutions going today.<br>
&lt;emilio> There's no point on allowing auto with scrollbar-width: none but not hidden for example<br>
</details>


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


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

Received on Wednesday, 20 November 2024 17:59:21 UTC