- From: Munira via GitHub <sysbot+gh@w3.org>
- Date: Mon, 12 May 2025 09:33:11 +0000
- To: public-css-archive@w3.org
Thanks @tabatkins , this makes sense. Then few open questions with this approach: - Since now the value reflects the most recent scroll in that direction, value `none` becomes unreachable expect of the initial state, should we leave it then or should we remove it? If we decide to remove `none`: 1. We can have `inline-start` and `block-start` as initial values. 2. Values `X`, `Y`, `block` and `inline` will always match, so there would be no point of having them. 3. if we have latin script and only vertical scroller, should we match `inline-start` initially? - As far as I understood, if we want to match the most recent scroll direction (not `none`) once we stop scrolling, then the value reflects the most recent scroll in that direction, e.g. if we scrolled `down` and then `right`, `scroll-direction: bottom` will still match after scrolling right. But then is there a use case when we want to hide/show some vertical scrolling specific content once we start scrolling horizontally? Then we might have 2 values, let's say `bottom` and `latest-bottom`, where one will still match after scrolling horizontally and another will only match if latest scrolling (not latest _vertical_ scrolling) was `bottom`. -- GitHub Notification of comment by tursunova Please view or discuss this issue at https://github.com/w3c/csswg-drafts/pull/12130#issuecomment-2871769914 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 12 May 2025 09:33:12 UTC