- From: jonjohnjohnson via GitHub <sysbot+gh@w3.org>
- Date: Tue, 11 Dec 2018 22:07:22 +0000
- To: public-css-archive@w3.org
Maybe someone from the microsoft team could way in on what went into the reasoning for their [-ms-scroll-limit](https://msdn.microsoft.com/en-us/library/jj127336(v=vs.85).aspx) property ([description](https://books.google.com/books?id=ouZdAlif4RwC&pg=PA185&lpg=PA185&dq=%22-ms-scroll-limit%22+property&source=bl&ots=n_RcOAsQkW&sig=Mdb3kRcr87UhjAxsE_pzMrzWQx0))? Seems like there could be crossover here. Though, more than limiting a scrollable area within a scroll container, I've often found myself just wanting to limit the placement of scrollbars within a scroll container, "pulling" the scrollbar tracks placement in from the containers edges, to leave room for many of these visually non scrolling areas, even if only sometimes non scrolling, like what google has called "hidey bars" that move in and out of view with scrolling direction. So fixed/sticky headers/footers/sidebars are never obfuscated by the scrollbar/track. Since we have `scrollbar-width`, what about `scrollbar-inset`/`scrollbar-insets`taking physical/logical offset values? -- GitHub Notification of comment by jonjohnjohnson Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3428#issuecomment-446380797 using your GitHub account
Received on Tuesday, 11 December 2018 22:07:24 UTC