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

Re: [csswg-drafts] [css-scrollbars][use-case] Real world product usage (#1969)

From: Ilya Streltsyn via GitHub <sysbot+gh@w3.org>
Date: Wed, 28 Jul 2021 15:26:59 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-888403691-1627486018-sysbot+gh@w3.org>
The problem that a potentially useful tool can mess up things if misused/abused seems a general problem rather than a specific tool problem. With the color-only approach promoted by the current spec, it's equally possible to make the scrollbar completely uninformative and useless by setting `scrollbar-color: black black` (let alone the fact that at least current Firefox 90 implementation seems to break the native behavior of scrollbar arrows on Windows 10, and that possible inability to handle hover state of the scrollbar thumb is "[probably fine](https://bugzilla.mozilla.org/show_bug.cgi?id=1460456#c7)").

To me, attempting to prevent web devs from "breaking" the scrollbars usability by restricting the tools more and more, seems to be much like adding more and more armor to the areas with most dots on this famous diagram:
![Ilustration of Survivorship Bias](https://upload.wikimedia.org/wikipedia/commons/thumb/b/b2/Survivorship-bias.svg/400px-Survivorship-bias.svg.png)
It's absolutely not guarranteed that, being unable to change scrollbar according to design/marketing demands, web developers will leave the native scrollbars untouched and will not try to _completely replace them_ by JS-based workarounds. Which would probably worse for UX/usability than minor visual changes to some native scrollbar parts. We can have a "must"-level warning for authors in the spec (like we have [for the `order` property](https://drafts.csswg.org/css-flexbox-1/#order-accessibility)), browser devtools can automatically check whether scrollbars remain functional or not (like Lighthouse checks the readability of text etc.), and, of course, we should educate designers and promote best practices. But trying to prevent misusing tools by artificially restricting their capacities doesn't seem a very productive way to me.

GitHub Notification of comment by SelenIT
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1969#issuecomment-888403691 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 28 July 2021 15:27:02 UTC

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