Re: [csswg-drafts] [css-overflow-4] Do not remove overflow: overlay (#6090)

> The choice of whether scrollbars should be overlay scrollbars or not is generally a user choice, not a web author choice. If the user chose overlay scrollbars at the OS level, overriding this decision at the author level is not very user-friendly (same with the opposite).

This should be first a choice of the developers before the users.

Let me argue. Let's say you have a web application and you have several groups stacked on top of each other that scroll to the right (horizontally). By defining "overlay" as an alias of "auto", the vertical scroll bar of the page will cause a hole on the right border of the interface.

What do you think will happen? Users will complain to the web developers that the interface is "glitched" and that the horizontally scrollable groups cut off before reaching the end of the window in width.

Maybe I'm wrong, and I sincerely hope I'm wrong, but the scrollbar-gutter feature doesn't seem to fix this problem at all and it will simply cause a deep and sincere sense of hatred among users because their favorite applications/websites are broken. Maybe there is a modern solution to this problem but it is funny to think that those who want the overlay alias have not proposed any alternative.

**"Excuse us, there is nothing we can do about it. This is a feature that has been removed by web browser developers."**

Here's what's going to happen. Do you really think about the web developers before you start removing features you consider "useless" or "unknown to you"? What right do you have to consider these features as unused or unknown? On what do you base such nonsense? Do you have any statistics on the use of the overlay value on the whole web? I don't think so.

The ones who will receive the complaints from the users will be without a doubt neither the developers of these browsers, nor the ones who decided to remove this feature, but us, developers.

I may sound like an angry person here, but at some point someone has to say it. Let me speak for all the web applications you are going to break. What alternative do we have before our web applications get broken by this change? 

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


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

Received on Tuesday, 18 April 2023 13:56:00 UTC