AlertIOS manages native iOS alerts, option sheets, and share dialogs
AppRegistry is the JS entry point to running all React Native apps. App
+
AppRegistry is the JS entry point to running all React Native apps. App
root components should register themselves with
AppRegistry.registerComponent, then the native system can load the bundle
for the app and then actually run the app when it's ready by invoking
AppRegistry.runApplication.
AppRegistry should be required early in the require sequence to make
sure the JS execution environment is setup before other modules are
-required.
AsyncStorage is a simple, asynchronous, persistent, global, key-value storage +
AsyncStorage is a simple, asynchronous, persistent, global, key-value storage system. It should be used instead of LocalStorage.
It is recommended that you use an abstraction on top of AsyncStorage instead of AsyncStorage directly for anything more than light usage since it operates globally.
This JS code is a simple facad over the native iOS implementation to provide -a clear JS API, real Error objects, and simple non-multi functions.
Fetches key and passes the result to callback, along with an Error if
-there is any.
Sets value for key and calls callback on completion, along with an
-Error if there is any.
Merges existing value with input value, assuming they are stringified json.
Not supported by all native implementations.
Erases all AsyncStorage for all clients, libraries, etc. You probably +a clear JS API, real Error objects, and simple non-multi functions.
Fetches key and passes the result to callback, along with an Error if
+there is any.
Sets value for key and calls callback on completion, along with an
+Error if there is any.
Merges existing value with input value, assuming they are stringified json.
Not supported by all native implementations.
Erases all AsyncStorage for all clients, libraries, etc. You probably don't want to call this - use removeItem or multiRemove to clear only your -own keys instead.
Gets all keys known to the system, for all callers, libraries, etc.
multiGet invokes callback with an array of key-value pair arrays that -matches the input format of multiSet.
multiGet(['k1', 'k2'], cb) -> cb([['k1', 'val1'], ['k2', 'val2']])
multiSet and multiMerge take arrays of key-value array pairs that match -the output of multiGet, e.g.
multiSet([['k1', 'val1'], ['k2', 'val2']], cb);
Delete all the keys in the keys array.
Merges existing values with input values, assuming they are stringified +own keys instead.
Gets all keys known to the system, for all callers, libraries, etc.
multiGet invokes callback with an array of key-value pair arrays that +matches the input format of multiSet.
multiGet(['k1', 'k2'], cb) -> cb([['k1', 'val1'], ['k2', 'val2']])
multiSet and multiMerge take arrays of key-value array pairs that match +the output of multiGet, e.g.
multiSet([['k1', 'val1'], ['k2', 'val2']], cb);
Delete all the keys in the keys array.
Merges existing values with input values, assuming they are stringified json.
Not supported by all native implementations.
Saves the image with tag tag to the camera roll.
@param {string} tag - Can be any of the three kinds of tags we accept: +
Saves the image with tag tag to the camera roll.
@param {string} tag - Can be any of the three kinds of tags we accept: 1. URL 2. assets-library tag - 3. tag returned from storing an image in memory
Invokes callback with photo identifier objects from the local camera
+ 3. tag returned from storing an image in memory
Invokes callback with photo identifier objects from the local camera
roll of the device matching shape defined by getPhotosReturnChecker.
@param {object} params - See getPhotosParamChecker.
@param {function} callback - Invoked with arg of shape defined by
getPhotosReturnChecker on success.
diff --git a/docs/datepickerios.html b/docs/datepickerios.html
index 656d0004b9b..3c42e0f546f 100644
--- a/docs/datepickerios.html
+++ b/docs/datepickerios.html
@@ -1,12 +1,12 @@
-
Use DatePickerIOS to render a date/time picker (selector) on iOS. This is
+
Use DatePickerIOS to render a date/time picker (selector) on iOS. This is
a controlled component, so you must hook in to the onDateChange callback
and update the date prop in order for the component to update, otherwise
the user's change will be reverted immediately to reflect props.date as the
-source of truth.
The currently selected date.
Maximum date.
Restricts the range of possible date/time values.
Minimum date.
Restricts the range of possible date/time values.
The interval at which minutes can be selected.
The date picker mode.
Valid modes on iOS are: 'date', 'time', 'datetime'.
Date change handler.
This is called when the user changes the date or time in the UI. +source of truth.
The currently selected date.
Maximum date.
Restricts the range of possible date/time values.
Minimum date.
Restricts the range of possible date/time values.
The interval at which minutes can be selected.
The date picker mode.
Date change handler.
This is called when the user changes the date or time in the UI. The first and only argument is a Date object representing the new -date and time.
Timezone offset in seconds.
By default, the date picker will use the device's timezone. With this +date and time.
Timezone offset in minutes.
By default, the date picker will use the device's timezone. With this parameter, it is possible to force a certain timezone offset. For -instance, to show times in Pacific Standard Time, pass -7 * 60.
A react component for displaying text which supports truncating -based on a set truncLength.
In the following example, the text will truncate -to show only the first 17 characters plus '...' with a See More button to -expand the text to its full length.
The styles that will be applied to the See More button. Default -is bold.
The caption that will be appended at the end, by default it is
-'See More'.
Text to be displayed. It will be truncated if the character length
-is greater than the truncLength property.
The styles that will be applied to the text (both truncated and -expanded).
The maximum character length for the text that will -be displayed by default. Note that ... will be -appended to the truncated text which is counted towards -the total truncLength of the default displayed string. -The default is 130.
Our first React Native implementation is ReactKit, targeting iOS. We are also
+
Our first React Native implementation is ReactKit, targeting iOS. We are also
working on an Android implementation which we will release later. ReactKit
apps are built using the React JS framework, and render directly to
native UIKit elements using a fully asynchronous architecture. There is no
diff --git a/docs/image.html b/docs/image.html
index f5295079da3..2bf6fa51871 100644
--- a/docs/image.html
+++ b/docs/image.html
@@ -1,4 +1,4 @@
-
A react component for displaying different types of images, +
A react component for displaying different types of images, including network images, static resources, temporary local images, and images from local disk, such as the camera roll.
Example usage:
Example usage:
accessibilityLabel - Custom string to display for accessibility.
accessible - Whether this element should be revealed as an accessible -element.
capInsets - When the image is resized, the corners of the size specified +element.
capInsets - When the image is resized, the corners of the size specified by capInsets will stay a fixed size, but the center content and borders of the image will be stretched. This is useful for creating resizable rounded buttons, shadows, and other resizable assets. More info:
testID - A unique identifier for this element to be used in UI Automation diff --git a/docs/interactionmanager.html b/docs/interactionmanager.html index 80e5a577ea3..d792085a220 100644 --- a/docs/interactionmanager.html +++ b/docs/interactionmanager.html @@ -1,4 +1,4 @@ -
InteractionManager allows long-running work to be scheduled after any +
InteractionManager allows long-running work to be scheduled after any interactions/animations have completed. In particular, this allows JavaScript animations to run smoothly.
Applications can schedule tasks to run after interactions with the following:
ListView - A core component designed for efficient display of vertically +
ListView - A core component designed for efficient display of vertically
scrolling lists of changing data. The minimal API is to create a
ListView.DataSource, populate it with a simple array of data blobs, and
instantiate a ListView component with that data source and a renderRow
@@ -30,22 +30,22 @@ event-loop (customizable with the pageSize prop). This breaks up t
work into smaller chunks to reduce the chance of dropping frames while
rendering rows.
How many rows to render on initial component mount. Use this to make it so that the first screen worth of data apears at one time instead of -over the course of multiple frames.
(visibleRows, changedRows) => void
Called when the set of visible rows changes. visibleRows maps
+over the course of multiple frames.
(visibleRows, changedRows) => void
Called when the set of visible rows changes. visibleRows maps
{ sectionID: { rowID: true }} for all the visible rows, and
changedRows maps { sectionID: { rowID: true | false }} for the rows
that have changed their visibility, with true indicating visible, and
-false indicating the view has moved out of view.
Called when all rows have been rendered and the list has been scrolled +false indicating the view has moved out of view.
Called when all rows have been rendered and the list has been scrolled to within onEndReachedThreshold of the bottom. The native scroll event is provided.
Threshold in pixels for onEndReached.
Number of rows to render per event loop.
An experimental performance optimization for improving scroll perf of large lists, used in conjunction with overflow: 'hidden' on the row -containers. Use at your own risk.
() => renderable
The header and footer are always rendered (if these props are provided) +containers. Use at your own risk.
() => renderable
The header and footer are always rendered (if these props are provided) on every render pass. If they are expensive to re-render, wrap them in StaticContainer or other mechanism as appropriate. Footer is always -at the bottom of the list, and header at the top, on every render pass.
(rowData, sectionID, rowID) => renderable +at the bottom of the list, and header at the top, on every render pass.
(rowData, sectionID, rowID) => renderable Takes a data entry from the data source and its ids and should return a renderable component to be rendered as the row. By default the data is exactly what was put into the data source, but it's also possible to -provide custom extractors.
(sectionData, sectionID) => renderable
If provided, a sticky header is rendered for this section. The sticky +provide custom extractors.
(sectionData, sectionID) => renderable
If provided, a sticky header is rendered for this section. The sticky behavior means that it will scroll with the content at the top of the section until it reaches the top of the screen, at which point it will stick to the top until it is pushed off the screen by the next section diff --git a/docs/mapview.html b/docs/mapview.html index 73a78c92243..5ca30fe62ac 100644 --- a/docs/mapview.html +++ b/docs/mapview.html @@ -1,5 +1,5 @@ -
Insets for the map's legal label, originally at bottom left of the map.
-See EdgeInsetsPropType.js for more information.
Maximum size of area that can be displayed.
Minimum size of area that can be displayed.
Callback that is called continuously when the user is dragging the map.
Callback that is called once, when the user is done moving the map.
When this property is set to true and a valid camera is associated
+
Insets for the map's legal label, originally at bottom left of the map.
+See EdgeInsetsPropType.js for more information.
Maximum size of area that can be displayed.
Minimum size of area that can be displayed.
Callback that is called continuously when the user is dragging the map.
Callback that is called once, when the user is done moving the map.
When this property is set to true and a valid camera is associated
with the map, the camera’s pitch angle is used to tilt the plane
of the map. When this property is set to false, the camera’s pitch
angle is ignored and the map is always displayed as if the user
diff --git a/docs/navigatorios.html b/docs/navigatorios.html
index 17f44b95fe6..94b564bb7fb 100644
--- a/docs/navigatorios.html
+++ b/docs/navigatorios.html
@@ -1,4 +1,4 @@
-
NavigatorIOS wraps UIKit navigation and allows you to add back-swipe +
NavigatorIOS wraps UIKit navigation and allows you to add back-swipe functionality across your app.
A route is an object used to describe each page in the navigator. The first
route is provided to NavigatorIOS as initialRoute:
React NativeresetTo(route) - Replaces the top it
initialRoute={...}
/>
),
-});NavigatorIOS uses "route" objects to identify child views, their props, +});
NavigatorIOS uses "route" objects to identify child views, their props, and navigation bar configuration. "push" and all the other navigation operations expect routes to be like this:
The default wrapper style for components in the navigator. A common use case is to set the backgroundColor for every page
The color used for buttons in the navigation bar
NetInfo exposes info about online/offline status
== iOS Reachability
Asyncronously determine if the device is online and on a cellular network.
NetInfo exposes info about online/offline status
== iOS Reachability
Asyncronously determine if the device is online and on a cellular network.
One of React Native goal is to be a playground where we can experiment with different architectures and crazy ideas. Since browsers are not flexible enough, we had no choice but to reimplement the entire stack. In the places that we did not intend to change, we tried to be as faithful as possible to the browser APIs. The networking stack is a great example.
XMLHttpRequest API is implemented on-top of iOS networking apis. The notable difference from web is the security model: you can read from arbitrary websites on the internet since there is no concept of CORS.
One of React Native goal is to be a playground where we can experiment with different architectures and crazy ideas. Since browsers are not flexible enough, we had no choice but to reimplement the entire stack. In the places that we did not intend to change, we tried to be as faithful as possible to the browser APIs. The networking stack is a great example.
XMLHttpRequest API is implemented on-top of iOS networking apis. The notable difference from web is the security model: you can read from arbitrary websites on the internet since there is no concept of CORS.
PixelRatio class gives access to the device pixel density.
There are a few use cases for using PixelRatio:
A width of 1 is actually pretty thick on an iPhone 4+, we can do one that's +
PixelRatio class gives access to the device pixel density.
There are a few use cases for using PixelRatio:
A width of 1 is actually pretty thick on an iPhone 4+, we can do one that's
thinner using a width of 1 / PixelRatio.get(). It's a technique that works
on all the devices independent of their pixel density.
You should get a higher resolution image if you are on a high pixel density device. A good rule of thumb is to multiply the size of the image you display @@ -6,7 +6,7 @@ by the pixel ratio.
Returns the device pixel density. Some examples:
In iOS, you can specify positions and dimensions for elements with arbitrary precision, for example 29.674825. But, ultimately the physical display only have a fixed number of pixels, for example 640×960 for iphone 4 or 750×1334 for iphone 6. iOS tries to be as faithful as possible to the user value by spreading one original pixel into multiple ones to trick the eye. The downside of this technique is that it makes the resulting element look blurry.
In practice, we found out that developers do not want this feature and they have to work around it by doing manual rounding in order to avoid having blurry elements. In React Native, we are rounding all the pixels automatically.
We have to be careful when to do this rounding. You never want to work with rounded and unrounded values at the same time as you're going to accumulate rounding errors. Having even one rounding error is deadly because a one pixel border may vanish or be twice as big.
In React Native, everything in JS and within the layout engine work with arbitrary precision numbers. It's only when we set the position and dimensions of the native element on the main thread that we round. Also, rounding is done relative to the root rather than the parent, again to avoid accumulating rounding errors.
A width of 1 is actually 2 physical pixels thick on an iPhone 4 and 3 physical pixels thick on an iphone 6+. If you want to display a line that's as thin as possible, you can use a width of 1 / PixelRatio.get(). It's a technique that works on all the devices independent of their pixel density.
You should get a higher resolution image if you are on a high pixel density device. A good rule of thumb is to multiply the size of the image you display by the pixel ratio.
In iOS, you can specify positions and dimensions for elements with arbitrary precision, for example 29.674825. But, ultimately the physical display only have a fixed number of pixels, for example 640×960 for iphone 4 or 750×1334 for iphone 6. iOS tries to be as faithful as possible to the user value by spreading one original pixel into multiple ones to trick the eye. The downside of this technique is that it makes the resulting element look blurry.
In practice, we found out that developers do not want this feature and they have to work around it by doing manual rounding in order to avoid having blurry elements. In React Native, we are rounding all the pixels automatically.
We have to be careful when to do this rounding. You never want to work with rounded and unrounded values at the same time as you're going to accumulate rounding errors. Having even one rounding error is deadly because a one pixel border may vanish or be twice as big.
In React Native, everything in JS and within the layout engine work with arbitrary precision numbers. It's only when we set the position and dimensions of the native element on the main thread that we round. Also, rounding is done relative to the root rather than the parent, again to avoid accumulating rounding errors.
A width of 1 is actually 2 physical pixels thick on an iPhone 4 and 3 physical pixels thick on an iphone 6+. If you want to display a line that's as thin as possible, you can use a width of 1 / PixelRatio.get(). It's a technique that works on all the devices independent of their pixel density.
You should get a higher resolution image if you are on a high pixel density device. A good rule of thumb is to multiply the size of the image you display by the pixel ratio.
Component that wraps platform ScrollView while providing +
Component that wraps platform ScrollView while providing integration with touch locking "responder" system.
Doesn't yet support other contained responders from blocking this scroll view from becoming the responder.
When true, the scroll view bounces horizontally when it reaches the end even if the content is smaller than the scroll view itself. The default @@ -17,7 +17,7 @@ wraps all of the child views. Example:
return ( contentContainer: { paddingVertical: 20 } - });
A floating-point number that determines how quickly the scroll view + });
A floating-point number that determines how quickly the scroll view decelerates after the user lifts their finger. Reasonable choices include - Normal: 0.998 (the default) - Fast: 0.9
When true, the scroll view's children are arranged horizontally in a row @@ -29,17 +29,17 @@ instead of vertically in a column. The default value is false.
When false, tapping outside of the focused text input when the keyboard is up dismisses the keyboard. When true, the scroll view will not catch taps, and the keyboard will not dismiss automatically. The default value -is false.
The maximum allowed zoom scale. The default value is 1.0.
The minimum allowed zoom scale. The default value is 1.0.
When true, the scroll view stops on multiples of the scroll view's size +is false.
The maximum allowed zoom scale. The default value is 1.0.
The minimum allowed zoom scale. The default value is 1.0.
When true, the scroll view stops on multiples of the scroll view's size when scrolling. This can be used for horizontal pagination. The default value is false.
Experimental: When true, offscreen child views (whose overflow value is
hidden) are removed from their native backing superview when offscreen.
This canimprove scrolling performance on long lists. The default value is
-false.
When true, the scroll view scrolls to top when the status bar is tapped. +false.
When true, the scroll view scrolls to top when the status bar is tapped. The default value is true.
An array of child indices determining which children get docked to the
top of the screen when scrolling. For example, passing
stickyHeaderIndices={[0]} will cause the first child to be fixed to the
top of the scroll view. This property is not supported in conjunction
-with horizontal={true}.
The current scale of the scroll view content. The default value is 1.0.
Callback called when the user finishes changing the value (e.g. when -the slider is released).
Callback continuously called while the user is dragging the slider.
Used to style and layout the Slider. See StyleSheet.js and
+
Callback called when the user finishes changing the value (e.g. when +the slider is released).
Callback continuously called while the user is dragging the slider.
Used to style and layout the Slider. See StyleSheet.js and
ViewStylePropTypes.js for more info.
Initial value of the slider. The value should be between 0 and 1. Default value is 0.
This is not a controlled component, e.g. if you don't update the value, the component won't be reseted to it's inital value.
The way to declare styles in React Native is the following:
The way to declare styles in React Native is the following:
A StyleSheet is an abstraction similar to CSS StyleSheets
Create a new StyleSheet:
A StyleSheet is an abstraction similar to CSS StyleSheets
Create a new StyleSheet:
Performance:
Use SwitchIOS to render a boolean input on iOS. This is
+
Use SwitchIOS to render a boolean input on iOS. This is
a controlled component, so you must hook in to the onValueChange callback
and update the value prop in order for the component to update, otherwise
the user's change will be reverted immediately to reflect props.value as the
source of truth.
If true the user won't be able to toggle the switch. -Default value is false.
Background color when the switch is turned on.
Callback that is called when the user toggles the switch.
Background color for the switch round button.
Background color when the switch is turned off.
The value of the switch, if true the switch will be turned on. +Default value is false.
Background color when the switch is turned on.
Callback that is called when the user toggles the switch.
Background color for the switch round button.
Background color when the switch is turned off.
The value of the switch, if true the switch will be turned on. Default value is false.
A react component for displaying text which supports nesting, +
A react component for displaying text which supports nesting,
styling, and touch handling. In the following example, the nested title and
body text will inherit the fontFamily from styles.baseText, but the title
provides its own additional styles. The title and body will stack on top of
@@ -25,7 +25,7 @@ each other on account of the literal newlines:
Used to truncate the text with an elipsis after computing the text layout, including line wrapping, such that the total number of lines does -not exceed this number.
This function is called on press. Text intrinsically supports press +not exceed this number.
This function is called on press. Text intrinsically supports press
handling with a default highlight state (which can be disabled with
suppressHighlighting).
When true, no visual change is made when text is pressed down. By default, a gray oval highlights the text on press down.
Used to locate this view in end-to-end tests.
In iOS, the way to display formatted text is by using NSAttributedString: you give the text that you want to display and annotate ranges with some specific formatting. In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.
A foundational component for inputting text into the app via a +
A foundational component for inputting text into the app via a keyboard. Props provide configurability for several features, such as auto- correction, auto-capitalization, placeholder text, and different keyboard types, such as a numeric keypad.
The simplest use case is to plop down a TextInput and subscribe to the
@@ -22,7 +22,7 @@ the native text input. The default should be fine, but if you're
potentially doing very slow operations on every keystroke then you may
want to try increasing this.
When the clear button should appear on the right side of the text view
If you really want this to behave as a controlled component, you can set this true, but you will probably see flickering, dropped keystrokes, -and/or laggy typing, depending on how you process onChange events.
If false, text is not editable. Default value is true.
Determines which keyboard to open, e.g.numeric.
If true, the text input can be multiple lines. Default value is false.
Callback that is called when the text input is blurred
(text: string) => void
Callback that is called when the text input's text changes.
Callback that is called when the text input is focused
The string that will be rendered before text input has been entered
The text color of the placeholder string
See DocumentSelectionState.js, some state that is responsible for +and/or laggy typing, depending on how you process onChange events.
If false, text is not editable. Default value is true.
Determines which keyboard to open, e.g.numeric.
If true, the text input can be multiple lines. Default value is false.
Callback that is called when the text input is blurred
(text: string) => void
Callback that is called when the text input's text changes.
Callback that is called when the text input is focused
The string that will be rendered before text input has been entered
The text color of the placeholder string
See DocumentSelectionState.js, some state that is responsible for maintaining selection information for a document
The default value for the text input
Timers are an important part of an application and React Native implements the browser timers.
requestAnimationFrame(fn) is the exact equivalent of setTimeout(fn, 0), they are triggered right after the screen has been flushed.
setImmediate is executed at the end of the current JavaScript execution block, right before sending the batched response back to native. Note that if you call setImmediate within a setImmediate callback, it will be executed right away, it won't yield back to native in between.
The Promise implementation uses setImmediate as its asynchronicity primitive.
One reason why well-built native apps feel so smooth is by avoiding expensive operations during interactions and animations. In React Native, we currently have a limitation that there is only a single JS execution thread, but you can use InteractionManager to make sure long-running work is scheduled to start after any interactions/animations have completed.
Applications can schedule tasks to run after interactions with the following:
Timers are an important part of an application and React Native implements the browser timers.
requestAnimationFrame(fn) is the exact equivalent of setTimeout(fn, 0), they are triggered right after the screen has been flushed.
setImmediate is executed at the end of the current JavaScript execution block, right before sending the batched response back to native. Note that if you call setImmediate within a setImmediate callback, it will be executed right away, it won't yield back to native in between.
The Promise implementation uses setImmediate as its asynchronicity primitive.
One reason why well-built native apps feel so smooth is by avoiding expensive operations during interactions and animations. In React Native, we currently have a limitation that there is only a single JS execution thread, but you can use InteractionManager to make sure long-running work is scheduled to start after any interactions/animations have completed.
Applications can schedule tasks to run after interactions with the following:
Compare this to other scheduling alternatives:
The touch handling system considers one or more active touches to be an 'interaction' and will delay runAfterInteractions() callbacks until all touches have ended or been cancelled.
InteractionManager also allows applications to register animations by creating an interaction 'handle' on animation start, and clearing it upon completion:
A wrapper for making views respond properly to touches. +
A wrapper for making views respond properly to touches. On press down, the opacity of the wrapped view is decreased, which allows the underlay color to show through, darkening or tinting the view. The underlay comes from adding a view to the view hierarchy, which can sometimes @@ -12,9 +12,8 @@ backgroundColor of the wrapped view isn't explicitly set to an opaque color /> </View> ); -},
Determines what the opacity of the wrapped view should be when touch is -active.
Called when the touch is released, but not if cancelled (e.g. by -a scroll that steals the responder lock).
The color of the underlay that will show through when the touch is +},
A wrapper for making views respond properly to touches. +
A wrapper for making views respond properly to touches. On press down, the opacity of the wrapped view is decreased, dimming it. This is done without actually changing the view hierarchy, and in general is easy to add to an app without weird side-effects.
Example:
Example:
Do not use unless you have a very good reason. All the elements that +
The Vibration API is exposed at VibrationIOS.vibrate(). On iOS, calling this
+
The Vibration API is exposed at VibrationIOS.vibrate(). On iOS, calling this
function will trigger a one second vibration. The vibration is asynchronous
so this method will return immediately.
There will be no effect on devices that do not support Vibration, eg. the iOS -simulator.
Vibration patterns are currently unsupported.
The most fundamental component for building UI, View is a
+
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
@@ -15,9 +15,9 @@ a default parent (flexDirection: 'column'), the children will fill the
but not the height.
Many library components can be treated like plain Views in many cases, for
example passing them children, setting style, etc.
Views are designed to be used with StyleSheets for clarity and
performance, although inline styles are also supported. It is common for
-StyleSheets to be combined dynamically. See StyleSheet.js for more info.
When true, indicates that the view is an accessibility element
For most touch interactions, you'll simply want to wrap your component in
+StyleSheets to be combined dynamically. See StyleSheet.js for more info.
When true, indicates that the view is an accessibility element
For most touch interactions, you'll simply want to wrap your component in
TouchableHighlight.js. Check out Touchable.js and
-ScrollResponder.js for more discussion.
In the absence of auto property, none is much like CSS's none
+ScrollResponder.js for more discussion.
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:
.cantTouchThis * { pointer-events: auto; } diff --git a/docs/webview.html b/docs/webview.html index e4377b39d05..f46762d43af 100644 --- a/docs/webview.html +++ b/docs/webview.html @@ -1,4 +1,4 @@ -