- From: Ilya Streltsyn via GitHub <sysbot+gh@w3.org>
- Date: Sat, 10 Jul 2021 06:47:24 +0000
- To: public-css-archive@w3.org
To me, it looks more like a duplicate of #2009, which was closed despite some objections in actively upvoted comments. But I don’t mind keeping any issue open for tracking use cases that are difficult to cover with the currently chosen approach. As such useful use cases, I’d mention distinct hover styles for the scrollbar track and thumb, rounded corners pf the thumb (Tweetdeck, one of the recent CSS-Tricks redesigns) and making scrollbar thumb visually consisent with other interactive elements (on CSS-Tracks, it was styled like the button, with gradient fill and pill-like shape). In general, the approach “let’s give people the tool they ask for, but prevent overusing it by restricting it so much that it becomes nearly impractical” is kind of premature optimization. The similar issue with the highly demanded `:has()` selector — basically disallowing it for the thing it was most needed for, the styling — made browser vendors not interested in implementing it for years. The alternative that devs had to resort to — jQuery-like JS solutions — likely had worse performance and usability implications than this restriction tried to avoid. I don’t want this happen to scrollbar styling too. -- GitHub Notification of comment by SelenIT Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2153#issuecomment-877581428 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 10 July 2021 06:47:27 UTC