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

Re: [csswg-drafts] [css-scrollbars][proposal] New "better" proposition for scrollbars (#2153)

From: Ilya Streltsyn via GitHub <sysbot+gh@w3.org>
Date: Wed, 28 Jul 2021 14:25:41 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-888353476-1627482340-sysbot+gh@w3.org>
@bmathwig I wholeheartedly agree that user experience is the most important (and with the [Priority of Constituencies principle](https://www.w3.org/TR/html-design-principles/#priority-of-constituencies) in general).

What I argue about is that depriving web developers of "good" (or at least "decent") ways to implement the still-popular feature is probably _not the best way to prevent them from implementing it._ They just would resort to "bad" (or even "awful") solutions like JS plugins. Such "workarounds" often lack basic native scrollbar features like keyboard accessibility, and IMO it worsens the user experience much more than, e.g., having rounded corners of the scrollbar thumb on Windows (like on TweetDeck, YouTube, CSS-Tricks.com, and many other popular products/resources).

Better long-term solution to this problem is, IMO, educating web designers and product owners about the importance of the UX and OS UI consistency. But the ability to _slightly_ modify the background or shape of the scrollbar thumb, while preserving its visual recognizability and all built-in functionality like reacting to hover state, seems at least an acceptable compromise to me.

-- 
GitHub Notification of comment by SelenIT
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2153#issuecomment-888353476 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 14:25:43 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:27:25 UTC