- From: jonjohnjohnson via GitHub <sysbot+gh@w3.org>
- Date: Sun, 25 Nov 2018 22:35:07 +0000
- To: public-css-archive@w3.org
Though I see that the spec doesn't exactly address the issue, I agree with the implementations in gecko/blinks, making an author responsible for handling the edge cases with either media queries or possibly intersection observers to enable "scroll chaining" when needed. I've noticed when using transforms/perspective/sticky/scrollbars for native-like interactions, there are complexities where your best solution is to create a scrolling element outside of the viewport or initial containing block, effectively faking the visual of a "scrollport" as the viewport ([example](https://output.jsbin.com/qunekib/quiet)). I'd be concerned about heuristics for zooms or viewport overflowing scrollers, especially after seeing the complexities in blink adding their [implicit root scroller](https://bugs.chromium.org/p/chromium/issues/detail?id=798719), instead of just saying, "hey, no scroll chaining up from this user scrollable element". -- GitHub Notification of comment by jonjohnjohnson Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3267#issuecomment-441480074 using your GitHub account
Received on Sunday, 25 November 2018 22:35:09 UTC