This is a read-only archive of the Framer Community on Facebook.

What is Framer? Join the Community
Return to index
Scott Criswell
Posted Feb 08 - Read on Facebook

Anyone else noticing doubleClick seems to perform more consistently than doubleTap? I have strange animation bugs with doubleTap that are completely resolved by switching to doubleClick. The only problem with that is that you cannot use doubleClick for a mobile prototype.

8 Comments

Koen Bok

DoubleClick is native and DoubleTap uses a timer. I can look into this. Any hints on how to find inconsistencies?

Scott Criswell

I'd be happy to put together a variant of the prototype I'm working on now and share it with you so you can see the issue.

Scott Criswell

Is doubleClick supposed to function on a mobile device? Doesn't work for me only doubleTap

Scott Criswell

Here's my demo framer project for you to review. Change "splitWindow.onDoubleClick" to "splitWindow.onDoubleTap" to see the issue. onDoubleClick works as is should.

Note: Drag the splitWindow up and down and then interact with both the doubleClick/Tap of the splitWindow and the splitToggle to see all of the behavioral bugs I'm experiencing. Again, onDoubleClick fixes every concern in this example.

http://share.framerjs.com/ck1ec9pjnqox/

Koen Bok

So doubleclick does not exist on mobile, because it's a native event and there are no clicks on mobile. But we made it confusing because with click we "automagically" make it work.

Our last gesture events release is an attempt to fix that. If you use any of those we guarantee they work on desktop and mobile (so Tap is Click or Touch etc).

Koen Bok

So I fixed one issue where DragStart was called too quickly (before movement), but in your prototype an issue still persists when you start a drag session while it's animating. The state then get messed up because the animation never ends. For cases like this I'd really recommend using states, they are simple and avoid all these issues.

Scott Criswell

OK, I'll take a look at states.

Scott Criswell

So to be clear doubleTap cannot be expected to function exactly the same as doubleClick with the obvious exception of doubleClick being a mouse click event and doubleTab being a mobile gesture.

We will need to use slightly different development best practices for each? For example in my little prototype doubleClick performs the interaction as expected but doubleTap does not (assuming both are being tested on a traditional desktop) and would be better designed with states as you suggested.

Read the entire post on Facebook