Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[css-overflow-4] give scrollbar-gutter the ability to decide whether overlay or classic scrollbars should be used instead of only the user agent #7716

Closed
karl-police opened this issue Sep 8, 2022 · 6 comments

Comments

@karl-police
Copy link

karl-police commented Sep 8, 2022

Apparently, scrollbar-gutter is finished and there's no possibility to create overlay scrollbars with it. Instead, the scrollbar-gutter definition, it says this:

Whether classic scrollbars or overlay scrollbars are used, the appearance and size of the scrollbar, and whether scrollbars appear on the start or end edge of the box, is UA defined.

 

I quote "is UA defined". Google Chrome added an experiment with that which can be toggled on the flags. It is an overlay scrollbar, but though it has some issues, and for some reason they gave it some animation and you can't control the style of it.

 

Why should only the user agent, be able to decide whether they see Classic Scrollbars or Overlay Scrollbars? So that would mean, the user using the browser would go to the settings to change it.

Aren't there ways to do those overlay scrollbars with the help of javascript or something? So why not give the web developer the choice to make those overlay scrollbars happen? But without JS.

What if the user agent wants to use both or let the website decide?

@karl-police karl-police changed the title [css-overflow-4] give scrollbar-gutter the ability to decide whetever overlay and classic scrollbars should be used instead of the User Agent [css-overflow-4] give scrollbar-gutter the ability to decide whetever overlay and classic scrollbars should be used instead of the user agent Sep 8, 2022
@karl-police karl-police changed the title [css-overflow-4] give scrollbar-gutter the ability to decide whetever overlay and classic scrollbars should be used instead of the user agent [css-overflow-4] give scrollbar-gutter the ability to decide whether overlay and classic scrollbars should be used instead of the user agent Sep 8, 2022
@Loirooriol
Copy link
Contributor

See #6090

@karl-police karl-police changed the title [css-overflow-4] give scrollbar-gutter the ability to decide whether overlay and classic scrollbars should be used instead of the user agent [css-overflow-4] give scrollbar-gutter the ability to decide whether overlay or classic scrollbars should be used instead of only the user agent Sep 8, 2022
@karl-police
Copy link
Author

karl-police commented Sep 8, 2022

See #6090

What am I supposed to see there? This is a different issue, where overflow: overlay doesn't matter anymore.

The issue here is scrollbar-gutter's definition regarding when a classic or an overlay scrollbar should be used.

@Loirooriol
Copy link
Contributor

That there was no implementation interest to have a feature to enforce overlay scrollbars, which is pretty close to what you are asking.

@karl-police
Copy link
Author

karl-police commented Sep 8, 2022

That there was no implementation interest to have a feature to enforce overlay scrollbars, which is pretty close to what you are asking.

implementation interest from who?

are you saying that there's not enough people requesting to have a feature to enforce overlay scrollbars?

@tabatkins
Copy link
Member

"Implementation interest" means interest from the implementors - that is, browser vendors. In other words, we specifically had some browser vendors object to this as a feature, indicating they would not implement it.

So yeah, #6090 has the details of the conversations that happened around this feature, making this a dupe.

@karl-police
Copy link
Author

"Implementation interest" means interest from the implementors - that is, browser vendors. In other words, we specifically had some browser vendors object to this as a feature, indicating they would not implement it.

So yeah, #6090 has the details of the conversations that happened around this feature, making this a dupe.

Where can I continue this conversation though?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants