![]() ![]() This document was produced by a group operating under the W3C Patent Policy. ![]() Including the spec code “css-overflow” in the title, like this:Īlternately, feedback can be sent to the ( archived) public mailing list document is governed by the 2 November 2021 W3C Process Document. It is inappropriate to cite this document as other than work in progress. Or obsoleted by other documents at any time. īy the CSS Working Group as a Working Draft using the Recommendationĭoes not imply endorsement by W3C and its Members. This section describes the status of this document at the time of its publication.Īnd the latest revision of this technical reportĬan be found in the W3C technical reports index at. 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?Īll 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.Īlso, note the mostly bulletproof table, affording sticky labels for rows and columns from. Which I *think, is a more desirable solution than the request here, even if I think it could sometimes have strange scrollbar visuals. Which I agree causes poor usability, but the solution might not be to move scrollbars to unintuitive areas of their scrollport.Ī request for "sticky" scrollbars has been brought up previously, #2252, addressing a similar problem, but its ask, I believe, would make scrollbars behave similar to the sticky position scheme against the edges of the scrolling elements scroll parent. This is mostly an issue if a nested scroller (not the scrollers content) is wider/taller than the scroller it is within. Second thought is that this issue primarily arises from poorly conceived layouts in the first place. And I'd hope standards would emphasis the usability afforded by familiarity in this case. 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. Right now, the trick that I use is something like this. ![]() In these sort of cases and others like (RTL languages) wouldn't it be great to have an option to change the position of the scrollbars? The situation is worse for mobile browsers because they generally have overlay scrollbars which only appear when you at least tap on the content.Ĭhrome on phones at least give a flash as to which containers have scrollbars and then it goes away. As a result, users don't realize that the content can be scrolled. Or when something like bootstrap responsive table is needed, which has a horizontal scroll in smaller screen-size.Ī lot of times, due to the amount of vertical content, the presence of a horizontal scrollbar is not known to the end user or they have to scroll further down where they can't see table headers anymore. Also, it has so much content that the space required on horizontal axis is more than what viewport width can provide. For example, consider a long table that forces a vertical scrollbar. From time to time, I have encountered cases where having a horizontal scrollbar at the top or left would be more helpful than having it at the bottom. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |