4 ms·
Could the issue be that you use an onClick event that has a well-known 400ms delay instead of a touchstart/touchmove event?
by melvinmt 14y ago
Could the issue be that you use an onClick event that has a well-known 400ms delay instead of a touchstart/touchmove event?
- lukifer 14y agoI'm quite sure that this developer knows the difference. :) Still, this does smell like it's a "feature", where the event is thrown away in an effort to prevent accidental touches or such. I imagine the bug is being ignored because of the difficulty of fixing it without removing the feature in question. Alas, I suspect that Apple's secrecy harms their process as well as ours: they probably live in such a bubble that they don't see these bugs as being problems. And I really wish Android was a better HTML5 alternative, but it's been problematic as well, as evidenced by Sencha's HTML5 Scorecards (we'll see with Chrome on Jelly Bean).