- From: Robert Flack via GitHub <sysbot+gh@w3.org>
- Date: Mon, 09 Sep 2024 19:45:49 +0000
- To: public-css-archive@w3.org
Just an update, to list proposed answers to the questions in the OP as something to try to resolve on, I propose the following: 1. The pseudo-element would be `::scroll-button(<direction>)` where direction is `up | down | left | right | block-start | block-end | inline-start | inline-end | prev | next`. `prev | next` map to the start / end in the axis having more scrollable length, with a preference to the block axis in the case of ties. 2. All buttons appear together before the scrolling element and before the scroll-marker-group in focus order. They are ordered by block-start, inline-start, block-end, inline-end in order. 3. Logical directions are a core part of the `<direction>` definition, see points 1 and 2. 4. They scroll by one "page" of scroll distance (e.g. similar to page up / down keys on the keyboard), which in most UA's is 85% of the scrollport size in the relevant axis but are adjusted by `scroll-padding`. -- GitHub Notification of comment by flackr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10722#issuecomment-2338945117 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 9 September 2024 19:45:50 UTC