- From: jonjohnjohnson via GitHub <sysbot+gh@w3.org>
- Date: Mon, 30 Apr 2018 02:07:16 +0000
- To: public-css-archive@w3.org
My first thought on this is that in most cases, it's not worth the confusion for a user to put scrollers on the top/left, when convention is bottom/right. And I'd hope standards would emphasis the usability afforded by familiarity in this case. Second thought is that this issue primarily arises from poorly conceived layouts in the first place. This is mostly an issue if a nested scroller (not the scrollers content) is wider/taller than the scroller it is within. Which I agree causes poor usability, but the solution might not be to more scrollbars to unintuitive areas of their scrollport. A request for "sticky" scrollbars has been brought up previously, https://github.com/w3c/csswg-drafts/issues/2252, addressing a similar problem, but it's ask, I believe, would make scrollbars behave similar to the sticky position scheme against the edges of the scrolling elements scroll parent. Which I *think, is a more desirable solution than the request here, even if I think it could sometimes have strange scrollbar visuals. Think when a horizontally scrollable table first scrolls into the viewport it's bottom sticking scrollbar would move in at the top edge of the table, though "mounting" to the bottom edge of the viewport until reaching the bottom edge of table? All in all, I'm guessing internal scrollers best practice should follow a rule of never being larger, in either axis, than the scroller (often viewport, using max-width/max-height with vw/wh) within which they are nested. If this rule of thumb is followed when crafting your layout, the only remaining usability issue I see is when a nested scroller can scroll horizontally and is shorter than the viewport, but until it is fully/mostly scrolled into view you cannot see the scrollbar on its bottom edge. Also, note the mostly bulletproof table, affording sticky labels for rows and columns from @SimplyPhy https://codepen.io/SimplyPhy/pen/oEZKZo. This type of table following the practice described above should be all we need? -- GitHub Notification of comment by jonjohnjohnson Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1293#issuecomment-385301394 using your GitHub account
Received on Monday, 30 April 2018 02:07:28 UTC