- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Fri, 27 Sep 2024 19:34:53 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-overflow-5] Scroll button pseudo-elements`, and agreed to the following: * `RESOLVED: add ::scroll-button() pseudo-elements to Overflow 5, as describe din the issue` <details><summary>The full IRC log of that discussion</summary> <TabAtkins> flackr: the ::scroll-button pseudos let authors easily add buttons scrolling partiuclar directions to a scroll container<br> <TabAtkins> flackr: last time the main thing tha tprevented us from resolving was a lack of clarity on how they would work<br> <TabAtkins> flackr: i have a specific list of answer to the open questions in my comment<br> <TabAtkins> flackr: basically, ::scroll-button(<direction>) syntax, taking logical or physical directions<br> <TabAtkins> flackr: the buttons come before the scrolling contents in focus order, all together<br> <TabAtkins> flackr: they scroll one "page", as determined by the UA similar to PgDn, in the relevant direction<br> <TabAtkins> flackr: I have opened a separate issue specifically to talk about the focus order of th epseudos with respect to each other<br> <lea> q?<br> <lea> q+<br> <TabAtkins> TabAtkins: I was gonna ask about that, happy to have it in a separate issue<br> <TabAtkins> lea: this seems reasanable. could we have a non-parenthetical version so you can style all of them the same way without enumerating them?<br> <TabAtkins> fantasai: that makes sense, but I'd keep the parens and let it be empty<br> <TabAtkins> lea: why?<br> <TabAtkins> fantasai: it's more like a universal selector<br> <TabAtkins> fantasai: we have other patterns similar to this<br> <TabAtkins> lea: we have precedent for un-paren'd pseudo-classes<br> <TabAtkins> fantasai: yeah, but pseudo-elements don't have that precedent. VT pseudos, for instance.<br> <TabAtkins> lea: Okay, no strong opinion.<br> <lea> I think `::scroll-button` is cleaner than `::scroll-button()` but not a hill I'd die on<br> <TabAtkins> flackr: proposed resolution, add ::scroll-button() pseudo-elements to Overflow 5, as describe din the issue<br> <TabAtkins> RESOLVED: add ::scroll-button() pseudo-elements to Overflow 5, as describe din the issue<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10722#issuecomment-2379932355 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 27 September 2024 19:34:54 UTC