- From: alexelias via GitHub <sysbot+gh@w3.org>
- Date: Fri, 12 Aug 2016 04:15:48 +0000
- To: public-css-archive@w3.org
This all sounds great, but I'd like to also reopen @rbyers's [earlier request](https://github.com/w3c/csswg-drafts/issues/92#issuecomment-193811483) to including a way to hide overlay scrollbars entirely and reserve no space. This is useful for image carousels, chat boxes, and for replacement by JS bespoke scrollers for contact lists and photo albums. Without vendor prefixes, it can only be achieved with [complex, bug-prone box tricks](https://blogs.msdn.microsoft.com/kurlak/2013/11/03/hiding-vertical-scrollbars-with-pure-css-in-chrome-ie-6-firefox-opera-and-safari/) or touch-handler fake scrollers. @tabatkins's objection was that we don't want to make it too easy to make sites unusable for users who prefer to click on the scrollbar, and he suggested: > For example, a "panning" overflow-style could hide the scrollbars when the device is capable of panning, and default to showing scrollbars otherwise. I think tying this to input capabilities is too weird. Some somewhat saner variants would be to tie it to overlay-or-not, or possibly scrollbar-absorbs-clicks-or-not. But, personally my preference would be to just have a `value3` that hides any scrollbar entirely and reserves no space, as I think having a rational platform is most important here. I've yet to run into a site abusing the existing vendor-prefixed properties to accidentally hide a useful desktop scrollbar, so I doubt standardizing the capability would lead to a problem either. -- GitHub Notification of comment by alexelias Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/92#issuecomment-239357456 using your GitHub account
Received on Friday, 12 August 2016 04:15:56 UTC