React NativeView
The most fundamental component for building UI, View is a
container that supports layout with flexbox, style, some touch handling, and
accessibility controls, and is designed to be nested inside other views and
to have 0 to many children of any type. View maps directly to the native
view equivalent on whatever platform React is running on, whether that is a
UIView, <div>, android.view, etc. This example creates a View that
wraps two colored boxes and custom component in a row with padding.
Views are designed to be used with StyleSheets for clarity and
performance, although inline styles are also supported.
Edit on GitHubProps #
onResponderRelease function #
accessible bool #
When true, indicates that the view is an accessibility element. By default, all the touchable elements are accessible.
accessibilityTraits AccessibilityTraits, [AccessibilityTraits] #
Provides additional traits to screen reader. By default no traits are provided unless specified otherwise in element
onAcccessibilityTap function #
When accessible is true, the system will try to invoke this function
when the user performs accessibility tap gesture.
onMagicTap function #
When accessible is true, the system will invoke this function when the
user performs the magic tap gesture.
testID string #
Used to locate this view in end-to-end tests.
onMoveShouldSetResponder 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.
onResponderGrant function #
onResponderMove function #
onResponderReject function #
accessibilityLabel string #
Overrides the text that's read by the screen reader when the user interacts with the element. By default, the label is constructed by traversing all the children and accumulating all the Text nodes separated by space.
onResponderTerminate function #
onResponderTerminationRequest function #
onStartShouldSetResponder function #
onStartShouldSetResponderCapture function #
onLayout function #
Invoked on mount and layout changes with
{nativeEvent: { layout: {x, y, width, height}}}.
pointerEvents enum('box-none', 'none', 'box-only', 'auto') #
In the absence of auto property, none is much like CSS's none
value. box-none is as if you had applied the CSS class:
box-only is the equivalent of
But since pointerEvents does not affect layout/appearance, and we are
already deviating from the spec by adding additional modes, we opt to not
include pointerEvents on style. On some platforms, we would need to
implement it as a className anyways. Using style or not is an
implementation detail of the platform.
style style #
backfaceVisibility enum('visible', 'hidden')
backgroundColor string
borderColor string
borderTopColor string
borderRightColor string
borderBottomColor string
borderLeftColor string
borderRadius number
borderTopLeftRadius number
borderTopRightRadius number
borderBottomLeftRadius number
borderBottomRightRadius number
borderStyle enum('solid', 'dotted', 'dashed')
opacity number
overflow enum('visible', 'hidden')
shadowColor string
shadowOffset {width: number, height: number}
shadowOpacity number
shadowRadius number
removeClippedSubviews bool #
This is a special performance property exposed by RCTView and is useful for scrolling content when there are many subviews, most of which are offscreen. For this property to be effective, it must be applied to a view that contains many subviews that extend outside its bound. The subviews must also have overflow: hidden, as should the containing view (or one of its superviews).
renderToHardwareTextureAndroid bool #
Whether this view should render itself (and all of its children) into a single hardware texture on the GPU.
On Android, this is useful for animations and interactions that only modify opacity, rotation, translation, and/or scale: in those cases, the view doesn't have to be redrawn and display lists don't need to be re-executed. The texture can just be re-used and re-composited with different parameters. The downside is that this can use up limited video memory, so this prop should be set back to false at the end of the interaction/animation.