- From: jonjohnjohnson via GitHub <sysbot+gh@w3.org>
- Date: Wed, 12 Dec 2018 23:38:22 +0000
- To: public-css-archive@w3.org
@franckyK I don't think anyone is arguing for the use of `scrollbar-width` to be used in environments where someone can or should be using the scrollbar. Think Android or iOS, there are scrollbar visuals, which aren't usable by means of "grabbing". We have browser features like `scroll-snap` that allow for things like optimized image carousels, or emulating what native iOS has as a "swipe view". When authors develop/design these interfaces, they should be using the `scrollbar-width` property responsibly to uphold a good experience for the user. This isn't a feature that has been requested for the motivation to remove scrollbars on a normal body scrolling website and make it harder for accessibility. This is a feature that is needed in place of many hacky css/js layout treatments that hide nuisance scrollbars, when the scrollbar, mostly as an ornament, is confusing a user. People hide scrollbars for good reasons. This feature is allowing that to be done cleanly, if the author decides it's good for the interface/user. Imagine the photos app on your phone, that surely animates/snaps as you swipe between individual photos, while maybe showing a sliver of the previous and next photos. Without `scrollbar-width: none` there would be a useless ornamental scrollbar covering the bottom of the screen without an actionable relationship to how many photos are in the sequence or which photo you are actually at (a scrollbar is not a paginator) when creating this interface in a browser. -- GitHub Notification of comment by jonjohnjohnson Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1958#issuecomment-446785519 using your GitHub account
Received on Wednesday, 12 December 2018 23:38:23 UTC