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

Re: [csswg-drafts] [css-scrollbars][css-scrollbars-1] Add to Scope section that we intend not to spec WebKit pseudo-element approach for reasons

From: Ilya Streltsyn via GitHub <sysbot+gh@w3.org>
Date: Sat, 07 Jul 2018 14:07:06 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-403218068-1530972426-sysbot+gh@w3.org>
I'm afraid that stating that "pseudo-elements for selecting specific parts of a scrollbar are unnecesssary for the documented use-cases" basing on actual `-webkit-scrollbar-*` pseudo-elements usage only can be kind of "survival bias". Developers who need more control over scrollbars than is easily achievable with cross-browser CSS have to resort to JS-based solutions. Quick look on some of the popular (3k+ stars) "custom scrollbar JS plugins" ([example 1](https://github.com/utatti/perfect-scrollbar), [example 2](https://github.com/malihu/malihu-custom-scrollbar-plugin)) shows that these use special styling of the scrollbar parts heavily, including graphical backgrounds and separate hover states for them.

Also. [the Tweetdeck example cited in the Wiki](https://www.w3.org/wiki/Css-scrollbars#TweetDeck) uses the color change _of the scrollbar thumb_ on hover (e.g. `.column-scroller::-webkit-scrollbar-thumb:hover { background-color: #8899a6 }`) and rounds its corners (`.scroll-styled-v::-webkit-scrollbar-thumb { border-radius: 5px; }`). Both aspects aren't yet addressed by the current  color-based proposal, but can be very important for the UI/UX consistency, especially on Windows.

-- 
GitHub Notification of comment by SelenIT
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2009#issuecomment-403218068 using your GitHub account
Received on Saturday, 7 July 2018 14:07:10 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 9 October 2019 08:16:45 UTC