Re: [csswg-drafts] [css-scrollbars-2] Introduce scrollbar-mode for autohide behavior in User Agents (#7421)

These developer comments of a Firefox scrollbar extension show the dilemma, we have:

https://addons.mozilla.org/en-US/firefox/addon/custom-scrollbars/?utm_source=addons.mozilla.org&utm_medium=referral&utm_content=search

> RE: Custom Width Options
> 
> Many users have asked me to include the ability to set a custom scrollbar width, which is currently possible on Chromium-based browsers. I'd LOVE to be able to do this, but currently the standard that Firefox is using does not support that functionality. If this is something that you want to see added to the standard so that Firefox can add this feature, consider leaving a like or comment on [this GitHub issue](https://prod.outgoing.prod.webservices.mozgcp.net/v1/3080b05ca0e965729505d0db13f2a0abcdb57654afb9238a3cc655a3ee705cea/https%3A//github.com/w3c/csswg-drafts/issues/6263).

Users of multiple systems and browsers need a way to unify this.
The purpose of standards is to define common features and prevent browsers from drifting apart. I still don't understand why a scrollbar is seomthing different?

> RE: More Customization Options
> 
> Some users have suggested more customization options, like setting specific widths or changing just the arrow button colours. While I would love to have more customization options and that type of customization is possible in other browsers, unfortunately, it's not possible in Firefox.
> 
> Firefox's scroll bar customization settings are in their very early "experimental" stages. I hope that the Firefox developers will eventually add a lot more customization options in the future and I will continue to add more features as they become available.

This shows, that undefined parts in the standard immediately lead to different behavior. Please stop this.
If there would be a standard users could demand that from the Firefox team. Without a standard they always have their excuses.

> RE: Facebook Issues
> 
> Some users have also brought up some issues with Facebook. When they introduced their new (and ugly) new design, they decided to build their own scrollbars instead of using the standard browser ones. They did this to have full control over the look and bahaviour of the scrollbars. Unfortunately, this means that the add-on is not able to customize their scrollbars.

This shows, that missing css attributes lead to the opposite of what you said it does. The developers want control over their design.

The solution is a hierarchical model exactly like it's defined in CSS.
It allows each level (webdev, browser, OS, user) to have it's control and higher levels can override lower levels.
The OS is only one level.
Additionally CSS attributes can be fine tuned for pages.
Some pages need different settings than others.

Again, non-existing attributes remove all the control from the user and each other level.

Fonts and scrollbars are basically the same problem, especially when it comes to accessibility.
Fonts can also be set in the OS. But this isn't a reason to force the same fonts and size in each and every application and all the displayed content.

Also, I wonder what you mean with "several OSes". MacOS and iOS? 
I can not get rid of the feeling, that you are an Apple fan boy.

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


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

Received on Wednesday, 5 July 2023 18:28:32 UTC