7705f521c8
* Change 'accessible' to align with React Native. * Add support for 'importantForAccessibility'. * Stop event propagation for keyboard-activated Touchables (nested Touchables now respond the same as when touch-activated). * Fix whitespace layout of nested Text elements. * Use 'div' for Text to improve TalkBack grouping. * Rewrite accessibility docs. Close #382 Fix #408
1.4 KiB
TouchableWithoutFeedback
Do not use unless you have a very good reason. All the elements that respond to press should have a visual feedback when touched. This is one of the primary reason a "web" app doesn't feel "native".
NOTE: TouchableWithoutFeedback supports only one child. If you wish to have
several child components, wrap them in a View.
Props
delayLongPress: ?number
Delay in ms, from onPressIn, before onLongPress is called.
delayPressIn: ?number
Delay in ms, from the start of the touch, before onPressIn is called.
delayPressOut: ?number
Delay in ms, from the release of the touch, before onPressOut is called.
disabled: ?boolean
If true, disable all interactions for this component.
onLongPress: ?function
onPress: ?function
Called when the touch is released, but not if cancelled (e.g. by a scroll that steals the responder lock).
onPressIn: ?function
onPressOut: ?function
pressRetentionOffset: ?{top: number, left: number, bottom: number, right: number}
When the scroll view is disabled, this defines how far your touch may move off of the button, before deactivating the button. Once deactivated, try moving it back and you'll see that the button is once again reactivated! Move it back and forth several times while the scroll view is disabled. Ensure you pass in a constant to reduce memory allocations.