- From: alexelias via GitHub <sysbot+gh@w3.org>
- Date: Mon, 05 Jun 2017 22:45:58 +0000
- To: public-css-archive@w3.org
> No, if you're providing an alternate scrollbar you'd just use overflow:hidden. The whole point of an alternate scrollbar is that it's controlling scrolling via JS, so there's no need for anything else. I think this would be really bad UX even on desktop. Mousewheel, trackpad, keyboard, selection autoscroll, drag-and-drop autoscroll, middle-click autoscroll and scroll-position historyitem restore ought to continue working as normal even if the scrollbar looks different, and each of those is very fined-tuned and basically intractable to reimplement identically in JS. IMO, the best practice is that every element supporting some variation on scrolling ought to be marked `overflow: scroll`, even if it scrolls unconventionally in certain respects. `overflow: hidden` is best reserved for use cases that are completely non-scrolling-like. > Unless you want an alternate scroller for everyone, and allow panning-friendly devices to scroll in their normal way with UA-provided scrolling? With, I suppose, a passive scroll listener to update the alternate scroller as well? Right, this is what I have in mind (panning, and every other non-scrollbar modality should keep working). I'm fine with the name `replacement`. -- GitHub Notification of comment by alexelias Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/419#issuecomment-306331643 using your GitHub account
Received on Monday, 5 June 2017 22:46:04 UTC