-
Notifications
You must be signed in to change notification settings - Fork 27
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
scrollbar-color CSS property #417
Comments
#419 issue for |
FYI here's some links to somethings missing above: WebKit WebKit |
As for accessibility impact the standard properties should be a net positive for accessibility as you can use user styles to more easily undo the styles. There's also better integration with the likes of |
It's also worth being aware there's partial implementations of both |
This is a pressure point for Firefox webcompat. |
Scrollbar Styling is also a common answer in https://2023.stateofcss.com/en-US/usage/#css_interoperability_features, and in https://2022.stateofcss.com/en-US/usage/#interoperability_features_freeform before that. |
Can we split this proposal into scrollbar-width & scrollbar-color for evaluation? |
I split out scrollbar-width into its own proposal: #571 |
Chromium intent to ship: https://groups.google.com/a/chromium.org/g/blink-dev/c/PkEsMirl2zE/m/ArphSa39AAAJ |
Test results for existing WPT for The specification does not have WPT annotations so I don't know how extensive the WPT coverage is (but it is a single property, so not too complicated). The existing WPT all use sRGB colors (plus named colors and currentColor). There are no tests with wide gamut colors etc. |
Safari failures seem to mainly relate to:
|
Safari doesn't have scrollbar-color support enabled, because the visual effect of the property isn't implemented atm. |
Safari's pass rate will be inflated as well because many of the tests are for invalidation which appears to pass in safari (because the property has no actual effect). I don't think WPT can effectively test the actual rendering as it's so platform dependent |
Thank you for proposing scrollbar-color CSS property for inclusion in Interop 2024. We wanted to let you know that this proposal was not selected to be part of Interop this year. This is because we got many more proposals than we could include in this year's project. Note that individual vendors may nevertheless choose to advance work in this area during the forthcoming year. We would welcome this proposal being resubmitted again next year if necessary. For an overview of our process, see proposal selection. Thank you again for contributing to Interop 2024! Posted on behalf of the Interop team. |
Description
Developers need a standard and cross-browser solution to style scrollbars for elements with
overflow: scroll;
.There are two alternatives to style scrollbars, the widely supported non-standard
::-webkit-scrollbar-*
pseudo-elements or the new standardscrollbar-*
properties defined in the CSS Scrollbars Styling Module spec. Both alternatives are not cross-browser supported.The non-standard
::-webkit-scrollbar-*
pseudo-elements supported by all browsers except Firefox. Whilescrollbar-width
andscrollbar-color
properties are supported only by Firefox.This is not an optimal situation for developers. We need a single solution implemented by all browsers.
Specification
https://drafts.csswg.org/css-scrollbars/
Open Issues
No response
Tests
https://wpt.fyi/results/css/css-scrollbars?label=master&label=experimental&aligned
Current Implementations
Standards Positions
No response
Browser bug reports
https://bugs.chromium.org/p/chromium/issues/detail?id=891944
Developer discussions
No response
Polls & Surveys
scrollbar-gutter
was mentioned in State of CSS 2023 and State of CSS 2022.This CSS property is not related to this spec but it is related to scrollbars in general.
Existing Usage
https://caniuse.com/css-scrollbar
https://chromestatus.com/metrics/css/timeline/popularity/763
https://chromestatus.com/metrics/css/timeline/popularity/680
Workarounds
Non-standard
::-webkit-scrollbar-*
pseudo-elements or JS libraries.Accessibility Impact
No response
Privacy Impact
No response
Other
No response
The text was updated successfully, but these errors were encountered: