I tend to get a bit obstinate when certain claims are made about the scrolling event… often people are referring to a time when it could indeed be problematic because of the device’s capabilities. These days, they’ll have no issue with it when the script is optimised.
In older versions of Mobile Safari scroll events were actually delivered at the end of the scroll, which made it impossible to make a JavaScript-based scroll effect.
Not true, it would just be very convoluted to keep track of any touch movements during panning.
In most browsers scroll events are delivered as “best-effort” and are not guaranteed to be delivered on every frame of the scroll animation!
Actually, you usually don’t even want that because you don’t need 60 frames a second to make a smooth looking animation. If anything, you’d throttle down the events to about 25 frames max. If the browsers starts skipping steps, the script is either just too demanding or other stuff is hogging resources.
Not to say a transform isn’t a neat approach, I just mildly object to these given “facts”…
