2e8eb652e1
Summary: This is a final diff in the stack, which makes us not send a bazillion events to js after it's been busy while an user dragged his finger on a screen (resulting in ~two events per frame). I made "touchMove" event to be coalescable, which makes us not send anything while dragging (since this makes both scroll events and touch move events coalesced and not being send until either next js frame or the next different touch event occurs). This change is far from perfect. The event name is a hard coded string and the coalescing works with some (reasonable) assumptions on internal structure of these touch events. Which may or may not be really true. It would be great if someone could comment on these. I'm thinking about making the touches more strongly typed. Any thoughts on this? public ___ //This diff is part of a larger stack. For high level overview what's going on jump to D2884593.// Reviewed By: nicklockwood Differential Revision: D2884595 fb-gh-sync-id: f3c2f13430679e2bf52e0c7a3689650b3acae42f |
||
|---|---|---|
| .. | ||
| Base | ||
| Executors | ||
| Layout | ||
| Modules | ||
| Profiler | ||
| React.xcodeproj | ||
| Views | ||