Re: [csswg-drafts] [css-conditional-5] Disambiguate scrollable/direction when along axis/towards edge (#12623)

The CSS Working Group just discussed `[css-conditional-5] Disambiguate scrollable/direction when along axis/towards edge`, and agreed to the following:

* `RESOLVED: Change 'direction' to 'scrolled', discuss keywords later`

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> noamr: We're currently using `scrollable` to say having the ability to scroll vertically or horizontally<br>
&lt;Rossen3> ack lea<br>
&lt;Zakim> lea, you wanted to react to fantasai<br>
&lt;fantasai> noamr: and then we are using `direction` for most recent scrolling direction<br>
&lt;fantasai> noamr: It felt that something was not totally finished in the naming<br>
&lt;fantasai> noamr: There's a few suggestions in the issue<br>
&lt;fantasai> noamr: Not super opinionated, but needs some work<br>
&lt;noamr> fantasai: miriam has suggested "scrolling" and "scrollable"; I think it kind of works<br>
&lt;noamr> fantasai: if it's now vs. recent if can be scrolling/scrolled<br>
&lt;moonira> q+<br>
&lt;noamr> fantasai: keywords for the scrolling direction can also use forward/backwards rather than x/y, or up/down/left/right rather than edges<br>
&lt;Rossen3> ack fantasai<br>
&lt;Rossen3> ack moonira<br>
&lt;fantasai> moonira: Just saw your comment, you mentioned scrollable as having none | x | y | block | inline<br>
&lt;fantasai> moonira: Do you mean changing those values as well, and remove values like top/bottom/etc?<br>
&lt;fantasai> fantasai: Wasn't clear to me from noam's comment about whether we were including the sides or not<br>
&lt;fantasai> moonira: scrollable is shipped, so prefer not to change that one, but for direction sounds great<br>
&lt;fantasai> moonira: If everyone is ok with Elika's proposal, can we decide to go with `scrolled` for last direction and use the keywords from that proposal?<br>
&lt;flackr> fantasai's proposal sgtm<br>
&lt;fantasai> moonira: Just want to make some progress here<br>
&lt;noamr> +1 to scrolled<br>
&lt;fantasai> Rossen3: Any additional opinions, or should we go with `scrolled` for last direction and keywords from the proposal?<br>
&lt;JoshT> +1<br>
&lt;Rossen3> ack fantasai<br>
&lt;fantasai> 'x-forward' vs 'x forward'<br>
&lt;fantasai> which style do we want?<br>
&lt;noamr> fantasai: there were independent proposals; up/down/left/right doesn't embed a direction but back/forward doesn't<br>
&lt;fantasai> flackr: what's that?<br>
&lt;fantasai> fantasai: physical axis with logical direction<br>
&lt;fantasai> fantasai: we do this for position-area, background-position<br>
&lt;flackr> I like hyphenated because up/right/down/left already have axis in them<br>
&lt;noamr> fantasai: the q is whether to have it space separated or hyphenated<br>
&lt;fantasai> fantasai: question is whether to use precombined hyphenated or combinable space-separated<br>
&lt;noamr> q+<br>
&lt;fantasai> miriam: Haven't thought through it, but prefer space-separated combinable<br>
&lt;djmarland> What would "left backward" do?<br>
&lt;fantasai> noamr: I suggest we resolve on `scrolled` as the descriptor, and we can ponder the additional keywords<br>
&lt;Rossen3> ack noamr<br>
&lt;fantasai> PROPOSED: Change 'direction' to 'scrolled', discuss keywords later<br>
&lt;fantasai> RESOLVED: Change 'direction' to 'scrolled', discuss keywords later<br>
&lt;fantasai> fantasai: Ok, let's come back to that though. It's confusing about whether scrolling towards or from the specified edge, so I think directional keywords would be better (in one form or another)<br>
</details>


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


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

Received on Wednesday, 10 September 2025 16:42:17 UTC