- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Sun, 01 Aug 2021 14:22:21 +0000
- To: public-css-archive@w3.org
> There is no valid functional use-case for that property, other than cosmetic benefits Please do not confuse "I don't know of a need for it" or "I don't need to" with "nobody has a need for it". Also, lots of features in CSS relate to appearance, so you could deem them cosmetic. That's also not the same as no use case. For wide scrollbars, there can be an aesthetic preference for them. There can be a functional preference for them. But the functional preference is a **user** preference, not an author preference. > a UA modification, which (as far as I know) is not covered under any standard Indeed. Standards do not cover user settings in user agents. Not because we don't want them to happen, but because it's outside of the range of things standards have influence on. Standards cannot do anything to force user agents to do anything. They willfully follow standards when they aid in interoperability, but UI or user settings are not part of that, and therefore not part of standards. Writing a standard about what user agents ought to do in the UI will do nothing to make it happen. This does not mean it won't happen, but writing it in a standard isn't how you get there. > and therefore may be inconsistently supported across browsers. Of course. Web standards are there to help user agents be interoperable with each other. Not to ensure that they are identical in all respects. Some browsers will offer lots of customizability, some will offer simple UI… They compete on that sort of things (among other things). > I guess there's not really much else I can do to convince you. If you have evidence that there is a meaningful amount of **authors** who are attempting to display wide scrollbars (and that doing so would not do a disservice to users), you're very welcome to make that case. -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6351#issuecomment-890529769 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 1 August 2021 14:22:23 UTC