![]() Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Therefore, a scrollbar is added to help the reader to scroll the content. This text is really long and the height of its container is only 100 pixels. Rossen_: We're are hour.The overflow property controls what happens to content that is too big to fit into an area. I assume this means for scrolling behavior and not for layout (e.g., size of scrollbars) RESOLVED: Align behavior of visibility:hidden with visible descendants for overflow:scroll to behave the same as overflow:hidden Rossen_: Obj to Align behavior of visibility:hidden with visible descendants for overflow:scroll to behave the same as overflow:hidden If want to try and lump in lets do that later. Rossen_: Since we're a minute past let's resolve on this. seems like pointer-events:none shouldn't effect keyboard-based scrolling? smfr: Also question on if pointer-events:none. Rossen_: Prop: Align behavior of visibility:hidden with visible descendants for overflow:scroll to behave the same as overflow:hidden People know you can select and drag to scroll overflow:hidden scrollers. Aligning with overflow:hidden would be similar behavior to something people know how to use. Maybe can write in same way as overflow:hidden which allows programmatic scrolling smfr: Behaves similar to if it's overflow:hidden. TabAtkins: If you were to make it scroll bounds it means can't be scrolled by anything. TabAtkins: final codepen has a scrollbar, but you can't scroll it directly element.scrollheight is same weither or not overflow:Scroll is hidden. Rossen_: Your definition, if I'm getting it correctly, for purposes of computing scroll bounds for scroller with visibility:hidden descendants are not counted as part of scroll boands for this scroller? emilio: FF behavior is same but we allow scrolling interactively the first time which is weird. smfr: Cannot interactively scroll, but can through programmatic and things happening on descendants. Should you be able to scroll if you interact? If programmatic movement should it move things around? ![]() smfr: You have overflow:scroll with visibity:hidden but a visble decendant. Topic: Should a visibility:hidden overflow:scroll be scrollable? RESOLVED: Align behavior of visibility:hidden with visible descendants for overflow:scroll to behave the same as overflow:hidden.The CSS Working Group just discussed Should a visibility:hidden overflow:scroll be scrollable?, and agreed to the following: In sum: If the hidden scroll container is "scrollable" it needs to be scrollable with every input method that normally works for visible scroll containers. (I do this all the time myself for small widgets on screen where I can't easily get keyboard focus to the correct place, since touch gesture scrolling on my trackpad is very unreliable.) To make scrolling work for this situation, the scrollbar itself would need to be rendered separate from the rest of the box. Of course, even that wouldn't guarantee accessibility for all users: some users still rely on grabbing the visible scoller in order to scroll. ![]() ![]() In this case, you'd need to make the visible child focusable, but at the same time something non-interactive that will bubble keyboard events up to the container.) (Now, some browsers aren't very good about making scrollable containers focusable by default even if they are visible, but the standard solution is to give the container tabindex="0". Which means there must be a keyboard-only way to get focus on the scroll container or its contents. I mean, if mouse-wheel users can scroll it, then keyboard users should be able to scroll it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |