You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Classic scrollbars are much more error-prone since they affect layout. However, writing tests may not be useful because they can seem to pass on a buggy UA just because it decides to use overlay scrollbars instead.
So it would be useful to have some way of forcing the UA to use classic scrollbars in these tests.
Note that browsers are already capable of that: Firefox uses classic scrollbars with the pref ui.useOverlayScrollbars=0, and Blink/WebKit seem to use classic scrollbars with this CSS hack:
CSS allows UAs to use either classic scrollbars or overlay scrollbars.
Classic scrollbars are much more error-prone since they affect layout. However, writing tests may not be useful because they can seem to pass on a buggy UA just because it decides to use overlay scrollbars instead.
So it would be useful to have some way of forcing the UA to use classic scrollbars in these tests.
Note that browsers are already capable of that: Firefox uses classic scrollbars with the pref
ui.useOverlayScrollbars=0
, and Blink/WebKit seem to use classic scrollbars with this CSS hack:So it would be a matter of exposing this behavior to WPT tests.
The text was updated successfully, but these errors were encountered: