- From: Ilya Streltsyn via GitHub <sysbot+gh@w3.org>
- Date: Wed, 04 Aug 2021 11:34:34 +0000
- To: public-css-archive@w3.org
@frivoal, @tabatkins thanks a lot for such detailed answers! Indeed, my example of the "solid black scrollbar" was quite nonsensical. What I really thought about was somehing like `scrollbar-color: black gray` which might look OK and consistent with a dark-themed UI, but confuse users because such scrollbar thumb doesn't provide any visual feedback in hover state anymore (at least, in Firefox 90 on Windows 10, in both light and dark OS UI themes). This seems to be an easy way to _slighly_ break the usability of the native UI part, without _any_ means fo fix it (other than resort to a JS-based custom solution). If only the same two scrollbar parts were available as pseudos (so all platforms whose scrollbars have a track and a thumb would likely be affected to about the same degree), the chance to do the same mistake would be similar, but the fix would be obvious. The question about default styleability of the pseudos is really tricky, but I assumed that the existing Chrome implementation has solved it somehow (yes, including some "magic", but this is not something new for CSS — styling form controls, including range inputs that look and behave quite "scrollbar-like" on many platforms, still suffers from the same issues). In general, the main reason why pseudo-based approach still may be worth discussing is the fact that it actually works in Chromium, which means for at least ~70% of users. If Chromium also plans to "unship" these pseudos and is not interested in pushing some subset/variation of them to the standards track, than, sure, their fate is sealed. The only thing I still ask for is not to leave authors without any tools to fix things that they can accidentally break with existing tools :) -- GitHub Notification of comment by SelenIT Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1969#issuecomment-892584756 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 4 August 2021 11:34:36 UTC