From e49175a335da2203f897a3425b93e6ab648c68c6 Mon Sep 17 00:00:00 2001 From: Website Deployment Script Date: Fri, 25 Mar 2016 03:27:12 +0000 Subject: [PATCH] Updated docs for next --- releases/next/docs/view.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/releases/next/docs/view.html b/releases/next/docs/view.html index c4269276d25..5f144ac7fb0 100644 --- a/releases/next/docs/view.html +++ b/releases/next/docs/view.html @@ -27,14 +27,14 @@ event is received, especially if a layout animation is in progress.

onMoveShouldSetResponder function #

onMoveShouldSetResponderCapture function #

onResponderGrant function #

For most touch interactions, you'll simply want to wrap your component in TouchableHighlight or TouchableOpacity. Check out Touchable.js, ScrollResponder.js and ResponderEventPlugin.js for more discussion.

onResponderMove function #

onResponderReject function #

onResponderRelease function #

onResponderTerminate function #

onResponderTerminationRequest function #

onStartShouldSetResponder function #

onStartShouldSetResponderCapture function #

pointerEvents enum('box-none', 'none', 'box-only', 'auto') #

Controls whether the View can be the target of touch events.

  • 'auto': The View can be the target of touch events.
  • 'none': The View is never the target of touch events.
  • 'box-none': The View is never the target of touch events but it's -subviews can be. It behaves like if the following classes +subviews can be. It behaves like if the view had the following classes in CSS:
    .box-none { pointer-events: none; } .box-none * { pointer-events: all; }
  • 'box-only': The view can be the target of touch events but it's -subviews cannot be. It behaves like if the following classes +subviews cannot be. It behaves like if the view had the following classes in CSS:
    .box-only { pointer-events: all; }