Delay for events on Touch Devices about framer

[tylerhowarth]

According to Google

...mobile browsers will wait approximately 300ms from the time that you tap the button to fire the click event. The reason for this is that the browser is waiting to see if you are actually performing a double tap.

My temporary solution is to include FastClick in to my index.html

Does anyone else think we should include something like FastClick in Framer?

[tylerhowarth]

Anyone have thoughts on this?

[joshpuckett]

Hey Tyler!

So, if you are building something exclusively for mobile devices, you can use the touchStart event, which fires instantly, as opposed to the click event. If you want both click and touch events, but want them to fire immediately on their respective platforms, you'll have to build in an event abstraction. Here's the general idea of how that would work:

if (touchDevice()) {

Events.TouchStart = "touchstart";
Events.TouchEnd = "touchend";
Events.TouchMove = "touchmove";

} else {

Events.TouchStart = "mousedown";
Events.TouchEnd = "mouseup";
Events.TouchMove = "mousemove";

}

view.on(Events.TouchStart, function() {

return console.log("Touch started");

});

[tylerhowarth]

@joshpuckett thanks! I will definitely try that out example out, because I end up using framer on web & mobile.

[koenbok]

Also, I already built these in (but did not publicly document them yet)
under the global Events object. You can check out events.coffee for more
info.

On Monday, June 17, 2013, Tyler Howarth wrote:

@joshpuckett https://github.com/joshpuckett thanks! I will definitely
try that out example out, because I end up using framer on web & mobile.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/33#issuecomment-19519291
.

[koenbok]

Fixed with Events.Click