Touch events on the mobile web are unfinished

Re:Touch events on the mobile web are unfinished by MatthewPhillips on Saturday September 15, 2012 @10:10PM (#4528014)

Another high-level event we need is scroll-end, or better, scroll-to-end. On scroll is very expensive on mobile and leads to lagginess.

[ Parent | on HN ]

Re:Touch events on the mobile web are unfinished by nevir on Sunday September 16, 2012 @12:28AM (#4528235)

I think taking a page from the native frameworks would be good here: Have a scroll start, scroll end, and nothing else. If you want to update during the scroll, you should be using requestAnimationFrame

[ Parent | on HN ]

Re:Touch events on the mobile web are unfinished by mistercow on Sunday September 16, 2012 @12:51AM (#4528276)

What's wrong with throttled on-scroll?

[ Parent | on HN ]

Re:Touch events on the mobile web are unfinished by nevir on Sunday September 16, 2012 @01:26AM (#4528352)

You can't do smart things on each frame (for ex, subbing in new content as the user scrolls)

You also don't know for sure when a scroll ends w/ the current impl

[ Parent | on HN ]

Re:Touch events on the mobile web are unfinished by mistercow on Monday September 17, 2012 @11:37AM (#4533045)

>You can't do smart things on each frame (for ex, subbing in new content as the user scrolls)

You wouldn't be able to do that with scroll-end either.

>You also don't know for sure when a scroll ends w/ the current impl

That makes sense, but that issue is orthogonal to performance.

[ Parent | on HN ]