Permalink
Browse files

RCTTouchHandler doesn't delay any touches anymore

Reviewed By: mmmulani

Differential Revision: D4418211

fbshipit-source-id: 07fdd81d975c6b65477e599e2dcb604b64556e9e
  • Loading branch information...
shergin authored and facebook-github-bot committed Jan 14, 2017
1 parent 8045a70 commit 930010ec9113a26e67373154bec3ba21901ae04e
Showing with 3 additions and 1 deletion.
  1. +3 −1 React/Base/RCTTouchHandler.m
@@ -53,10 +53,12 @@ - (instancetype)initWithBridge:(RCTBridge *)bridge
_reactTouches = [NSMutableArray new];
_touchViews = [NSMutableArray new];
// `cancelsTouchesInView` is needed in order to be used as a top level
// `cancelsTouchesInView` and `delaysTouches*` are needed in order to be used as a top level
// event delegated recognizer. Otherwise, lower-level components not built
// using RCT, will fail to recognize gestures.
self.cancelsTouchesInView = NO;
self.delaysTouchesBegan = NO; // This is default value.
self.delaysTouchesEnded = NO;
self.delegate = self;
}

2 comments on commit 930010e

@brentvatne

This comment has been minimized.

Show comment
Hide comment
@brentvatne

brentvatne Jan 15, 2017

Collaborator

any context around this?

Collaborator

brentvatne replied Jan 15, 2017

any context around this?

@shergin

This comment has been minimized.

Show comment
Hide comment
@shergin

shergin Feb 8, 2017

Contributor

@brentvatne After landing epic c68a708 we found that <NavigatorIOS> stoped working because of delaying "ends" of touches. So, we turn if off because we have no idea why we should delay it.

Do you have any concerns?

Contributor

shergin replied Feb 8, 2017

@brentvatne After landing epic c68a708 we found that <NavigatorIOS> stoped working because of delaying "ends" of touches. So, we turn if off because we have no idea why we should delay it.

Do you have any concerns?

Please sign in to comment.