- From: jonjohnjohnson via GitHub <sysbot+gh@w3.org>
- Date: Tue, 07 Aug 2018 16:53:40 +0000
- To: public-css-archive@w3.org
@tabatkins thanks for taking the time to respond. And if the stance is to not suggest or dictate that browsers handle the scrolling the same between the two scenarios, that is ok by me, I'm just glad to be on the same page here and have an answer. Sorry that my language/examples weren't very self-explanatory. IMHO definitely think the smooth scrolling is **not** _natural-looking_ for it's use case. Here is a link http://output.jsbin.com/micaz/ to a js implementation of what many native apps create for both "swiping" inertial movement as well as "tappable" execution of that movement. They both feel _natural_ and they use the same/consistent "timing function". Try swiping horizontally or vertically on the red block. Try tapping on the red block. This exhibits a different set of behaviors than the less idea inconsistencies from what we see in the native scrolling solution. I'll bring this up to individual browsers, because from what I remember firefox uses quite a linear function for smooth scrolling and is the most "jarring" in this case. I'm only putting a dog in this fight because scrolling seems to be a more efficient alternative to transforms and custom scroll/touch event javascript for this type of ui. I think consistency would help us here. Also, the original topic of this thread wasn't exactly where this ended, so I hope my derailing hasn't prematurely closed the issue, though I see the original topic as just as equally a no-go. -- GitHub Notification of comment by jonjohnjohnson Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/157#issuecomment-411126446 using your GitHub account
Received on Tuesday, 7 August 2018 16:53:45 UTC