-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Why is return false
required?
#74
Comments
I don't see a problem with doing it. @JedWatson ? |
PRs accepted |
@dcousens yes thanks, but given that that's the default on Github that's not particularly helpful :-) could you perhaps point me to the part of the code I should start looking at? |
https://github.com/JedWatson/react-tappable/blob/master/src/TappableMixin.js#L68 - however I'll need a test case to understand, as at this stage, I don't understand why that advice is there unless you're somehow handling |
Thanks! For one, capturing all touch events that bubble up to |
@ljharb shall we close? |
I’d prefer it remain open until someone (myself, maintainers, or someone else) can fix it. That the issue is old doesn’t make it any less of an issue :-) |
Per https://github.com/JedWatson/react-tappable#native-events, it seems like you're recommending using
return false
from an event handler to prevent Tappable from handling the event.However, it's a common best practice (and one my company enforces in its own codebase) to never
return false
from an event handler, and to always only explicitly callpreventDefault
/stopPropagation
/stopImmediatePropagation
on the event object.Would it be possible to make Tappable respect
preventDefault
on the event object such thatreturn false
isn't required?The text was updated successfully, but these errors were encountered: