- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 28 Aug 2024 16:55:52 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-overflow-5] Scroll button pseudo-elements`. <details><summary>The full IRC log of that discussion</summary> <bramus> flackr: other major UI component frequent in carousels is having butotns that scroll you through the content<br> <bramus> … also in scrollers in general sometimes<br> <bramus> …next/prev page, scroll up/down, …<br> <bramus> … proposal is to allow devs to create these with a pseudo-element<br> <bramus> … few options for what that might look lik<br> <TabAtkins> Big +1 on this, with the only caveat being that we super need this ability captured in a property *as well* which we can put on normal elements (with some suitable restrictions for a11y/usability)<br> <bramus> … and many open questions<br> <bramus> … e.g. focus order<br> <bramus> … seen examples of many different way of setting up these buttons<br> <florian> q+<br> <bramus> … want to get some attention on this to figure out if we would be happy to pursue this<br> <TabAtkins> q+<br> <SebastianZ> q+<br> <bramus> … and also some thoughts on specific questions<br> <astearns> ack florian<br> <astearns> q+<br> <bramus> florian: feedback on general idea: on the one hand yes, ppl do add these buttons<br> <bramus> … proposal goes much broader<br> <bramus> … for scroll buttons, reminds me of sth that I wanted to do when overlay scrollbars were new<br> <bramus> … because those scrollbars hide themselves, I wanted to add styles on the element so that users could se ethat it was scrollable<br> <bramus> … gave up beacuse I was fightnig the UI<br> <bramus> … similarly the trend is no longer to have scroll up/down buttons … these are useful and users can bring them back (OS setting) or is this a feature devs should bring back?<br> <bramus> … feel that is is unforutnate tha twe are fighthing back thorugh author space on featuers that UAs have removed<br> <bramus> flackr: in most cases where authors these, they look nothing like the thing the UA provides<br> <bramus> … main use case is to recreate native scrollbars<br> <florian> s/UAs have removed/UAs have removed, then again it is useful<br> <bramus> … probably are cases that do that, but mostly site specific things<br> <bramus> florian: fact that they look different is not necessarily diagnostic<br> <bramus> … I wouldnt have done that if browser kept original UI<br> <bramus> q+<br> <astearns> ack TabAtkins<br> <bramus> TabAtkins: like it, dropped syntax nit suggestion in the issue<br> <bramus> … the ability to trigger scrolls in whatever direction should be dropped onto a property so that we can put these on real elements too<br> <bramus> … having pseudos makes sense too<br> <florian> s/I wouldnt have done that if browser kept original UI/what I used to do back in the day also looked very different from the removed browser UI, I wouldnt have done that if browser kept original UI<br> <bramus> … figuring out restrictions is a little bit more complicated on those elements, so having only pseudos is fine too<br> <bramus> flackr: can do this with invokeaction on buttons<br> <bramus> TabAtkins: sounds reasonable<br> <astearns> ack SebastianZ<br> <bramus> SebastianZ: also am reminded of the popover approach<br> <bramus> … fits more to HTML so that we could introduce HTML attrs that would trigger scroll and then those elements could be style in any way<br> <bramus> astearns: want to address q3: absolutely<br> <bramus> … should design so authors can use scroll-start and scroll-end<br> <astearns> ack astearns<br> <astearns> ack bramus<br> <TabAtkins> bramus: Addressing lforian's remark<br> <TabAtkins> bramus: where he wanted to recreate classic scrollobars, think that's part of another discussion we already have an issue for<br> <florian> q+<br> <TabAtkins> bramus: where authors want control over overlay vs classic scrollbars<br> <TabAtkins> bramus: so maybe something to discuss in that issue<br> <argyle> hehe, looks like scroll buttons https://usercontent.irccloud-cdn.com/file/08ng5J3C/CSSWG%20zoom%20screenshot<br> <astearns> ack florian<br> <TabAtkins> florian: I wasn't so much pointing out that authors want to recreate classic scrollbars, but rather react to scrollbars being less useful as time goes by<br> <bramus> fantasai: i understand the desire to create these buttons using css<br> <bramus> … proposal is probably way too ??<br> <astearns> s/??/simplistic/<br> <bramus> … how much are you going to scroll by? fragment? page? part of page? section? next scroll marker?<br> <bramus> … lot of different amounts<br> <bramus> … q about relation to each other and what order to they appear compared to other pseudos?<br> <bramus> … lot of option questions<br> <TabAtkins> It's more than two, fwiw<br> <bramus> … proposal for 2 pseudos with page-up/down is a bit too simple to addres sproblem space<br> <bramus> … dont have a good ?? do we want to make this more complicated now or? – dont know what makes sens here<br> <bramus> … but see a lot of variation of what users want to do and think we need to capture those needs<br> <joshtumath> s/??/solution<br> <bramus> flackr: did mention everything you mentioned as a list of open questions<br> <bramus> … definitely undespecified at this moment<br> <bramus> … q is not to resolve, but for me to go formulate anwsers to all those questions and then take it back<br> <bramus> astearns: I suggest yes: work on the questions and need to figure out the details<br> <bramus> florian: do think it is worth exploring this<br> <bramus> … also UAs, make scrollbars useful please<br> <bramus> astearns: we not only need the questions<br> <bramus> … we need the group of usecases that we are trying to solve<br> <bramus> … maybe a group of usecases that is out of scope<br> <florian> s/it is worth exploring this/it is worth exploring this, authors will do this anyway, and it'll be more robust if we provide features in that space that help<br> <bramus> … discussing things in terms of what the author wants to do<br> <bramus> flackr: excellent feedback<br> <bramus> astearns: so we take this back?<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-2315844785 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 28 August 2024 16:55:52 UTC