4 ms·
The impact this makes on perceived speed is impressive. However, a word of caution. We tried this for a while and found it interfered with scrolling behaviour
by joahua 14y ago
The impact this makes on perceived speed is impressive.
However, a word of caution. We tried this for a while and found it interfered with scrolling behaviour on link-heavy pages, not to mention making event capture for swipeable elements difficult.
The technique is a useful one to be aware of, but I'd be wary of using a library for this - it didn't work out for us, and I'll hazard it is unlikely to work as well it initially appears to.
That initial 300ms speedup is astounding, though :)
- mattcg 14y agoI recently changed the way touch events are observed - bubbling listeners are used instead of capturing listeners. This fixed a problem we had with scrolling libraries. Have you tried the latest version?
- kalms 14y agoIt also conflicts with tap/click markers, when initiating animations on click event.
- mattcg 14y agoWill you file an issue with a reduced test case please?
- kalms 14y agoIt's specific to the iPad. The marker indicating a tap, will show on specific UI elements, since everything is shifting due to the animation. The case is from Google's implementation, not this one. Not really something we can do anything about - it's an edge case.