- From: Andy Earnshaw via GitHub <sysbot+gh@w3.org>
- Date: Thu, 13 Dec 2018 10:27:26 +0000
- To: public-css-archive@w3.org
@jonjohnjohnson thanks for providing more use cases. The one about still being able to see the content as it scrolls "outside" is an interesting one that I hadn't thought of. @upsuper this is mostly about giving developers more flexibility over the appearance of scrollbars and the behaviour of scroll containers. You may feel that there are workarounds to problems like this, but they always come with tradeoffs. Here's a gif animation of the grid I'm working on at the moment:  The grid, as I explained in https://github.com/w3c/csswg-drafts/issues/3397, is highly optimised. It's using custom scrollbars at the moment, but I am hoping to implement native scrollbars if your previous suggestion doesn't cause any issues. The row/column labels are rendered in a separate elements, but all the cells are rendered in a single container. You can see that rows 15, 25 and columns 15, 25 are "frozen", so the cells in those frozen columns do not change when you scroll horizontally, but do change when you scroll vertically. This means the scroll area is defined by the darker border going across the grid. Our custom scrollbars aren't currently confined to this area, but it's one of the upcoming changes planned. There would be no way to confine native scrollbars to that area without using a separate container for the scrollable area, but this would massively increase complexity in our codebase. I hope that clarifies the issue better. -- GitHub Notification of comment by andyearnshaw Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3428#issuecomment-446918439 using your GitHub account
Received on Thursday, 13 December 2018 10:27:34 UTC