- From: 張俊芝 via GitHub <sysbot+gh@w3.org>
- Date: Thu, 08 May 2025 02:34:17 +0000
- To: public-css-archive@w3.org
> Count me in and I think it's important to allow scroll axis to vary independently of the writing mode. My personal website has a multi-column layout for languages in LTR-TTB writing mode, and it should be scrolled horizontally. Thank you for your attention to this issue. The discussion on this topic has been partially superseded by [Setting the primary scrolling direction for a scroll container](https://0.0.39.76/). I completely agree with your perspective—the mouse wheel scrolling direction should indeed be independent of the writing-mode. This would be beneficial not only for your example case but also for other scenarios, such as a horizontal image carousel within a TBB (top-to-bottom) writing-mode webpage. However, in the new issue, the working group seems inclined against introducing a new CSS property at this stage, instead considering a rule to tie wheel scrolling direction to writing-mode. I suggest you reiterate your concerns in that thread to strengthen the case for a dedicated CSS property. > This CSS property should not change how `wheel` events are dispatched in response to wheel rotations --- it's always `deltaY` and positive means the user rotates the wheel towards oneself on Windows (in LTR-TTB and most browsers, this means the content below is made visible). Agreed. The spec doesn’t mandate default behavior for wheel scrolling—it’s entirely defined by browser implementations. Thus, preserving deltaY values while altering their behavior wouldn’t conflict with any existing standards. > I think `wheel-scroll-axis` is the better name. I’m neutral about explicitly including "wheel" in the property name. Including it could make the property’s real-world application more intuitive, while omitting it maintains broader logical consistency and future extensibility. After all, the property’s **sole purpose** is to **hint** at the primary scrolling axis—nothing more. (For an omnidirectional scroll devices where all directions are equally accessible, browsers could ignore this property entirely without special handling.) -- GitHub Notification of comment by Zhang-Junzhi Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4380#issuecomment-2861388049 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 8 May 2025 02:34:18 UTC