- From: jonjohnjohnson via GitHub <sysbot+gh@w3.org>
- Date: Thu, 16 May 2019 02:27:41 +0000
- To: public-css-archive@w3.org
If two completely independent scrollers sit side by side, I’ve simply not nested one in the other. This is how I understand your use case. No scroll chaining behavior is even needed if not nested. However, if conditionally one might want scrolling to chain, then nesting is a great way to not have to retarget scroll events with js between two independent scrollers. In my example, if sometimes the height of an environment/browser is tall enough that the aside would never overflow/scroll itself, then it can be good UX to afford scrolling over that area to affect the main (outer) scroller. This is how users have historically understood scrolling from atop fixed positioned headers or sidebars. So from a rwd perspective, enabling scroll chain inhibition based upon the aside actually overflowing seems like an often clean and desirable solution. -- GitHub Notification of comment by jonjohnjohnson Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3349#issuecomment-492892321 using your GitHub account
Received on Thursday, 16 May 2019 02:27:44 UTC