Re: [csswg-drafts] [css-scrollbars] Interaction between scrollbar-color and scrollbar-width with ::-webkit-scrollbar (#9856)

The CSS Working Group just discussed `[css-scrollbars] Interaction between scrollbar-color and scrollbar-width with ::-webkit-scrollbar`, and agreed to the following:

* `RESOLVED: If either scrollbar-width or scrollbar-color are anything other than initial values, then we ignore legacy -webkit-scroll pseudos`

<details><summary>The full IRC log of that discussion</summary>
&lt;astearns> ack luke<br>
&lt;fantasai> luke: I implemented the scrollbar properties in Chrome<br>
&lt;fantasai> luke: These properties, as implemented in Chrome, take precedence over the legacy -webkit-scrollbar styling<br>
&lt;fantasai> luke: That decision was kindof arbitrary, but based on feeling that the standard properties should take precedence even though it's not the same properti<br>
&lt;fantasai> luke: There's no specced behavior, would be good to get something in the spec wrt specifics<br>
&lt;fantasai> luke: at least wrt precedence<br>
&lt;astearns> ack florian<br>
&lt;fantasai> florian: Agree. When we drafted up the spec, we made an explicit decision not to spec those pseudos<br>
&lt;luke> q+<br>
&lt;fantasai> florian: it is a question of what to do when they are specified<br>
&lt;fantasai> florian: Proposed that if the new properties have anything other than their initial value, then the old ones don't work<br>
&lt;fantasai> florian: gives a good migration path<br>
&lt;fantasai> florian: limited effect<br>
&lt;fantasai> florian: easy to test<br>
&lt;fantasai> florian: and doesn't require saying anything special about how the legacy things work<br>
&lt;astearns> ack luke<br>
&lt;fantasai> luke: Interop has only included scrollbar-width, not scrollbar-color<br>
&lt;fantasai> luke: reason is that scrollbar-color is harder for WebKit to implement<br>
&lt;florian> q+<br>
&lt;fantasai> luke: but it means that webkit would have scrollbar-width but not scrollbar-color<br>
&lt;astearns> ack florian<br>
&lt;fantasai> luke: I would lean towards either one replaces the pseudos<br>
&lt;fantasai> florian: Agree, and I don't think we can distinguish between altering colors or width<br>
&lt;fantasai> florian: if you try to use a standard property that happens to not be implemented, then it wouldn't have an effect<br>
&lt;fantasai> florian: but using either or both should replace<br>
&lt;fantasai> astearns: smfr's comment is either as well<br>
&lt;fantasai> PROPOSED: If either scrollbar-width or scrollbar-color are anything other than initial values, then we ignore legacy -webkit-scroll pseudos<br>
&lt;luke> +1<br>
&lt;fantasai> RESOLVED: If either scrollbar-width or scrollbar-color are anything other than initial values, then we ignore legacy -webkit-scroll pseudos<br>
</details>


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


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 3 April 2024 23:35:55 UTC