The CSS Scrollbars spec allows authors to style scrollbars by specifying their colors and thickness. This spec adds the following two properties. The scrollbar-color property provides the capability of changing the color scheme of scrollbars so they fit better into the particular style of a web page. The scrollbar-width property allows the use of narrower scrollbars that may be more suitable for some use cases, or even to hide the scrollbars completely without affecting scrollability.
These are already supported inside of Firefox so shouldn't present much of a risk. It's possible that if Safari doesn't support them this could lead to some level of fragmentation between the legacy pseudo styles and the standard properties.
The value of scrollbar-width influences other properties such as scrollbar-gutter which take the scrollbar's thickness as reference. There might be conflicts between these properties and Chromium's own ::-webkit-scrollbar pseudo-elements that serve a similar purpose. This is partially addressed by these standard properties taking precedence inside of Chromium and WebKit.
These properties are easy for developers to take advantage of many will already be using them for Firefox support.
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
This should have no impact on WebView applications. It will simply allow customising the colours of scrollbars if they apply the necessary styles.
Both properties will show up in dev tools with auto complete support. Scrollbar color will also have the color swatch show up for both values.
The existing Web Platform Tests are not exhaustive. Internal tests are implemented where necessary. Results: https://wpt.fyi/results/css/css-scrollbars
Shipping on desktop | 121 |
DevTrial on desktop | 118 |
Shipping on Android | 121 |
DevTrial on Android | 118 |
Shipping on WebView | 121 |
Open questions about a feature may be a source of future web compat or interop issues. Please list open issues (e.g. links to known github issues in the project for the feature specification) whose resolution may introduce web compat/interop risk (e.g., changing to naming or structure of the API in a non-backward-compatible way).
No anticipated spec changes, this is already shipping in Firefox for a long time.The CSS Scrollbars spec allows authors to style scrollbars by specifying their colors and thickness. This spec adds the following two properties. The scrollbar-color property provides the capability of changing the color scheme of scrollbars so they fit better into the particular style of a web page. The scrollbar-width property allows the use of narrower scrollbars that may be more suitable for some use cases, or even to hide the scrollbars completely without affecting scrollability.
These are already supported inside of Firefox so shouldn't present much of a risk. It's possible that if Safari doesn't support them this could lead to some level of fragmentation between the legacy pseudo styles and the standard properties.
The value of scrollbar-width influences other properties such as scrollbar-gutter which take the scrollbar's thickness as reference. There might be conflicts between these properties and Chromium's own ::-webkit-scrollbar pseudo-elements that serve a similar purpose. This is partially addressed by these standard properties taking precedence inside of Chromium and WebKit.
These properties are easy for developers to take advantage of many will already be using them for Firefox support.
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
This should have no impact on WebView applications. It will simply allow customising the colours of scrollbars if they apply the necessary styles.
Both properties will show up in dev tools with auto complete support. Scrollbar color will also have the color swatch show up for both values.
The existing Web Platform Tests are not exhaustive. Internal tests are implemented where necessary. Results: https://wpt.fyi/results/css/css-scrollbars
Open questions about a feature may be a source of future web compat or interop issues. Please list open issues (e.g. links to known github issues in the project for the feature specification) whose resolution may introduce web compat/interop risk (e.g., changing to naming or structure of the API in a non-backward-compatible way).
No anticipated spec changes, this is already shipping in Firefox for a long time.Will scrollbar-color work on overlay scrollbars on macOS? It does in Firefox.
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAE-V8gBRP%2B11PMQSzs%3DLkUJWFnGTXvn5%2B%2Bx%2BWzX82i5sDqSEjw%40mail.gmail.com.
--
> I'm guessing we're missing ways to test if the styles were applied. Is that correct?> If so, can you file relevant WPT bugs to make sure we'd be able to expand coverage in the future?
Yeah I'll take a look into filing those bugs, as I understand it there's APIs missing to enable the common scrollbar implementation and you'd then need some form of pixel test or as you say an API to check that the scrollbar has the relevant colours.
> Also, it seems like Safari is passing many of the tests despite not having shipped this. The same is true for stable Chrome. Might be worthwhile to take a look and make sure the tests are actually testing the feature..
Lots of the tests are repaint tests so just make sure that when implemented it handles various cases (lots of them cases that I've come across while implementing). When the properties aren't supported lots of the repaint tests will pass as they rely on the properties in both the actual and expected. I'm not sure on the best way to avoid this?
LGTM2
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAL5BFfVj_Rzhx%2BK0yocJDprbjUuuzvdf1khQgk0qZYaYiV4UJg%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/a85b6a9c-cf1e-4ec1-a776-f1455c861822%40chromium.org.
LGTM3, with or without support in Android WebView depending on
what you and Torne decide (good catch by torne). Make sure it's
properly set in chromestatus depending on what you choose.
/Daniel
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/3f99b284-7978-49e7-abea-a359a1246f7dn%40chromium.org.