- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 05 Mar 2025 17:35:39 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-overflow-5] Default UA styles for scroll markers and scroll buttons`, and agreed to the following: * `RESOLVED: Default styling for scroll markers will match default styling for links. Default styling for scroll buttons will match default styling for buttons (and appearance will apply accordingly).` <details><summary>The full IRC log of that discussion</summary> <fantasai> flackr: We want to have a reasonable default styling for scroll markers and buttons, so they're visible<br> <fantasai> flackr: Our suggestion is to make scroll buttons to render like buttons, including handling 'appearance'.<br> <fantasai> flackr: and scroll markers would look like links<br> <fantasai> flackr: since they're interactive etc.<br> <TabAtkins> q+<br> <astearns> ack TabAtkins<br> <fantasai> TabAtkins: you did bring up question of appearance?<br> <fantasai> flackr: I implemented it, think it should<br> <fantasai> TabAtkins: agree<br> <astearns> ack fantasai<br> <kbabbitt> fantasai: the interesting question is whether the scroll markers match the ? pseudo class<br> <TabAtkins> :visited/:link<br> <kbabbitt> fantasai: technically they can't because :link by itself selects elements but not pseudos<br> <kbabbitt> fantasai; wondering what we want to do about that<br> <fantasai> s/;/:/<br> <fantasai> TabAtkins: So if page author changes their :link style, wouldn't change scroll markers?<br> <fantasai> fantasai: right<br> <chrishtr> q+<br> <fantasai> flackr: agree that would be nice... open to suggestions?<br> <JoshT> q+<br> <chrishtr> q-<br> <fantasai> astearns: If we don't find a way of having link styling apply to scroll marker, then what we're doing is requiring authors to add the ::scroll-marker selector to their link styling block<br> <fantasai> fantasai: which they're not going to remember to do<br> <fantasai> JoshT: Why are they being styled as links rather than buttons?<br> <fantasai> flackr: They scroll to content, just like regular links do<br> <chrishtr> it seems unlikely to me that developers won't notice that these Pseudos have the wrong colors, and then go fix it<br> <fantasai> JoshT: In the past, authors probably would have implemented as buttons; but I see the logic<br> <fantasai> TabAtkins: it depends what you're doing. Carousel dots, more like buttons; but for ToC, more like a link.<br> <chrishtr> the colors being wrong will make their scroll markers look invisible or totally wrong in prominent site ui<br> <fantasai> JoshT: What is the aria role?<br> <fantasai> flackr: They're tabs, with scroll marker group being the tablist<br> <fantasai> astearns: Should we resolve on this, and then try to figure out link styling? Or is this a fundamental question we need to solve?<br> <fantasai> fantasai: the goal of default styling is to make it visible... if not visible, not a good thing?<br> <fantasai> TabAtkins: As chrishtr points out, authors will almost always tweak them anyway<br> <fantasai> TabAtkins: so they're going to notice if looks bad on the page.<br> <fantasai> TabAtkins: same as if they put a blue background; will notice links are invisible<br> <fantasai> TabAtkins: so probably fine<br> <fantasai> astearns: Whether or not fine, could resolve today on default styling for scroll markers matching link styling, and scroll buttons taking button styling<br> <chrishtr> +1 to this proposed resolution<br> <fantasai> astearns: anything about appearance?<br> <fantasai> TabAtkins: appearance applies to scroll buttons same as regular buttons<br> <fantasai> PROPOSED: Default styling for scroll markers will match default styling for links. Default styling for scroll buttons will match default styling for buttons (and appearance will apply accordingly).<br> <fantasai> RESOLVED: Default styling for scroll markers will match default styling for links. Default styling for scroll buttons will match default styling for buttons (and appearance will apply accordingly).<br> <fantasai> flackr: I'll open a separate issue for the :link-matching<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10935#issuecomment-2701628083 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 5 March 2025 17:35:40 UTC