W3C home > Mailing lists > Public > public-css-archive@w3.org > July 2021

Re: [csswg-drafts] [css-scrollbars][css-scrollbars-1] Using scrollbar-color to tint the scrollbar (#5651)

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Wed, 21 Jul 2021 16:54:35 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-884340651-1626886474-sysbot+gh@w3.org>
The CSS Working Group just discussed `single-color scrollbar-color`, and agreed to the following:

* `RESOLVED: Defer to L2`

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> Topic: single-color scrollbar-color<br>
&lt;fantasai> github: https://github.com/w3c/csswg-drafts/issues/5651<br>
&lt;lea> sorry, was muted<br>
&lt;TabAtkins> fantasai: so one thing discussed is whether scrollbar-color should accept a single color, auto-generating the second color from the first<br>
&lt;TabAtkins> fantasai: another is around allowing 'auto' as a keyword in the two-value syntax, explicitly triggering auto-generation of the other color<br>
&lt;TabAtkins> fantasai: We put it on the agenda to ask if there was interest in allowing this<br>
&lt;emilio> I'd prefer not to add this unless there's strong author demand for it<br>
&lt;Rossen_> q?<br>
&lt;emilio> Not opposed per se but...<br>
&lt;smfr> q+<br>
&lt;fantasai> lea: I think there should be some defined algorithm for UA to generate other color<br>
&lt;fantasai> lea: reasonable for authors to define which color they want to alter, and UA to define other color<br>
&lt;fantasai> lea: Would prefer that option rather than specifying only one color and having magic other color<br>
&lt;fantasai> TabAtkins: ...<br>
&lt;fantasai> lea: Should be possible to specify one color<br>
&lt;fantasai> smfr: Wanted emilio to clarify, want single color to be invalid?<br>
&lt;TabAtkins> s/.../note that the spec currently requires two colors, so we'd first have to agree to allow only one color before the rest becomes relevant/<br>
&lt;fantasai> emilio: So far, Firefox requires 2 colors, and I haven't seen anyone particularly complain about that<br>
&lt;fantasai> smfr: I'm not opposed to a single color, but some ambiguity around whether lightening or darkening to generate the other color<br>
&lt;fantasai> smfr: esp with dark mode<br>
&lt;fantasai> smfr: might need to specify somehow<br>
&lt;lea> q+<br>
&lt;TabAtkins> I'm on the side of "just have the author provide both" (aka no spec change), I think<br>
&lt;Rossen_> ack smfr<br>
&lt;fantasai> lea: wrt dark mode and whether UA darkens or lightens<br>
&lt;fantasai> lea: that has to depend on the color as well<br>
&lt;fantasai> lea: defined which direction to go, then what do you do when author specifies black?<br>
&lt;fantasai> smfr: That's my point, there has to be a defined threshold where UA flips lightening vs darkening<br>
&lt;fantasai> smfr: maybe dark mode is not relevant, mayb authors provide different colors<br>
&lt;lea> q+<br>
&lt;Rossen_> ack lea<br>
&lt;fantasai> lea: I think we're discussing minutiae of specifying a single color<br>
&lt;fantasai> lea: but there's no consensus on whether this is desirable<br>
&lt;fantasai> emilio: Same issue that smfr mentions is already a thing with accent-color<br>
&lt;fantasai> emilio: Scrollbar-color already needs to synthesize other colors, e.g. for :hover effects<br>
&lt;fantasai> emilio: If there's a strong desire to auto-generate track color... I'd rather not<br>
&lt;fantasai> emilio: Authors might get what they want in some browsers and something different in other browser<br>
&lt;fantasai> smfr: Ideal way to specify would be to just use color-5 functions<br>
&lt;fantasai> smfr: Similar to ridge/groove<br>
&lt;TabAtkins> Yeah, unlike accent-color, this is a place where we absolutely know where and how each color is going to be used. Auto-generating colors would be purely a convenience, not a necessity like in accent-color.<br>
&lt;fantasai> s/groove/groove situation<br>
&lt;fantasai> fantasai: main question is, do we want to do this or do we want to defer<br>
&lt;fantasai> Rossen_: what's the consensus?<br>
&lt;fantasai> smfr: I think it's nice to have, but fine to defer to scrollbars-2<br>
&lt;fantasai> emilio: same<br>
&lt;fantasai> Rossen_: proposed to defer to l2, any objections?<br>
&lt;fantasai> RESOLVED: Defer to L2<br>
&lt;fantasai> Rossen_: Encourage folks to engage on the issue and continue discussion there<br>

GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5651#issuecomment-884340651 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 21 July 2021 16:54:37 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:39 UTC