W3C home > Mailing lists > Public > public-css-archive@w3.org > October 2016

Re: [csswg-drafts] [css-overflow] Add mechanism for disabling scrollbars

From: alexelias via GitHub <sysbot+gh@w3.org>
Date: Fri, 07 Oct 2016 18:04:45 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-252320845-1475863482-sysbot+gh@w3.org>
> (particularly ones without a mousewheel, which at least allows 
vertical "panning").

The problem is OSes in general do not necessarily provide a hook to 
tell us whether a touchscreen, mousewheel or touchpad is present.  We 
can confirm one exists once we get an input event, but prior to that 
we have no real idea (and we can never prove the negative).  We'd be 
forced to rely on crude heuristics.

>  it's more obviously necessary to provide user affordances, and 
those manually-added affordances are more likely to be tested

The main use I have in mind is precisely developers who want to 
manually provide an alternate scrollbar affordance (e.g. contact list 
big-letter scrollbar).  Your proposal raises the risk of 
double-scrollbar glitches, then.  You'd be forcing webdevs to detect 
whether the UA scrollbar is present or not in order to disable their 
superior bespoke scrollbar...

> Then maybe we can also have a less-conveniently-named value that 
actually turns off scrollbars all the time, which makes it clearer 
what the author's responsibilities are.

Well, that seems a bit complicated, but I guess I could tolerate that 
outcome if that's what can get consensus.

-- 
GitHub Notification of comment by alexelias
Please view or discuss this issue at 
https://github.com/w3c/csswg-drafts/issues/419#issuecomment-252320845 
using your GitHub account
Received on Friday, 7 October 2016 18:04:53 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:04 UTC