Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Question: onTap vs onClick. How to support both correctly?

See original GitHub issue

Hello

It seems that mobile browsers are able to handle click events. (However, iOS does some strange things see https://github.com/facebook/react/issues/2055)

So what I don’t understand is what’s the advantage of tap over click exactly?

In an application that should handle both mouse and touch events (responsive websites, or websites for laptops with touch screens), what should I do? use both onClick and onTap at the same time?

Issue Analytics

State:
Created 8 years ago
Comments:7 (4 by maintainers)

Top GitHub Comments

7reactions

dcousenscommented, Jan 11, 2017

Just use onTap, you don’t need onClick at all

2reactions

slorbercommented, Jan 12, 2017

@dcousens there are cases where you may want to differentiate between a click and a tap and not always handle the 2 the same way.

However I think the easiest would probably be to check the event type my callback receive on such case, so I can be fine if the lib triggers onTap for both events