3 ms·
It feels like you are using click for touch events. Which causes a ~300ms delay only on mobile phones. Makes me a little concerned about what other "common" hy
by peregrine 12y ago
It feels like you are using click for touch events. Which causes a ~300ms delay only on mobile phones.
Makes me a little concerned about what other "common" hybrid bugs you've missed. Is this your first rodeo with Hybrid apps or have you pushed them to production?
- nwienert 12y agoThere's a bug on the hamburger menu that's actually not the 300ms delay but seems like it. Everything else avoid the 300ms delay. We are using react-tappable[0] as a mixin into many of our components that allows a nice onTap={this.handleTap} usage. It is alpha. For example, I need to fix behavior that allows you to overflow scroll the entire body, which will require some thought and care in it's implementation, but I've already gotten it most the way there. More optimizations will come. As far as rodeo's it's not my first with hybrid though, I made a large mobile hybrid site in 2u.fm (now deceased, it avoided the 300ms delay though :)), and with my previous employer's site in production quite a bit. [0] https://github.com/JedWatson/react-tappable https://github.com/JedWatson/react-tappable