W3C home > Mailing lists > Public > public-css-archive@w3.org > May 2017

Re: [csswg-drafts] [css-ui-4][css-overflow] Suggestion: "Overflow styling" / Scrollbar styling

From: Xidorn Quan via GitHub <sysbot+gh@w3.org>
Date: Sun, 07 May 2017 06:29:20 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-299685473-1494138557-sysbot+gh@w3.org>
I'm feeling disappointed on that a feature mistakenly exposed to the web ends up needing to be implemented everywhere for interop.

I don't think doing the scrollbar pseudo-element is a good idea. OSs continuously evolve their scrollbars to provide better user experience. macOS and Ubuntu, IIRC, both have quite different scrollbar structure than that on Windows. Having something like this specified may make it harder for browsers to have decent behavior on different platforms.

Also, different OSs having different scrollbar structure also means testing interop is harder, because you would need to take not only engines but also platforms into account.

Actually, it is already not fully interop among platforms for Blink. `::-webkit-scrollbar-button` doesn't have any effect on macOS while it works on Windows.

>  <dael> TabAtkins: Oh no. We can't remove. They're used more than possible to kill.

I doubt this.

>From the document [Blink principles of web compatibility](https://docs.google.com/document/d/1RC-pBBvsazYfCNNUSkPqAVpSpNJ96U8trhNkfV0v9fk/edit#), it seems there are various aspects taken into account when deciding whether Blink wants to commit some breakage, not just the use counter.

It seems to me that removing this
* would mostly be a cosmetic breakage, which is generally safer than other kinds of breakage, and
* may actually give users more consistent experience on their platform, which could improve user experience, and
* aligns browsers behavior with less overall effort.

For web developers, I don't think the current situation, that it is not even fully interop among platforms even within a single engine, is very helpful. Existing usages may already fail to take different platforms into consider.

If we really want this kind of feature, I think we should think about some better design, rather than just accept whatever happens to exist, especially given that its origin thinks it's a bad idea and wants to deprecate it.

GitHub Notification of comment by upsuper
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/107#issuecomment-299685473 using your GitHub account
Received on Sunday, 7 May 2017 06:29:26 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:12 UTC