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

> we still reject exposing a large set of pseudos for scrollbars

There seems to be a bit of ambiguity in the current resolution: is it the fact that it's _pseudos_ or the fact that there is a _large_ set of them that is problematic? Are there chances that e.g. just two pseudos (one for the scrollbar track, potentially including arrows if the system UI has them, and one for the thumb — like with the range input) would be OK if this happens to cover >80% of real life usage, or is any number of pseudos a complete no-go? Regarding the performance issues mentioned in the discussion, wouldn't they occur as well if the set of scrollbar-related properties needs to expand to account for hover states and other aspects potentially important for both users and designers that aren't covered with the current draft yet?

Currently, rounded corners of the thumb and its hover state seem to be the most actively used aspects of scrollbar customization that can easily be done with pseudos, but are hard or nearly impossible to do with property-based approach. The latter is quite important for usability (visual feedback that scrollbar is active), and the former may be one of those UI details that are probably not so important for users, but are particularly "sensitive" for many designers, like the infamous "dotted focus ring" of links etc.

And speaking about people not complaining about lack of scrollbar customization in Firefox, the hard truth might be not that they are satisfied with status quo, but that due to Firefox's record low market share its "full support" became not so important, like it previously happened with IE:(

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


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Saturday, 31 July 2021 09:44:04 UTC