Animated
The Animated library is designed to make animations fluid, powerful, and easy to build and maintain. Animated focuses on declarative relationships between inputs and outputs, with configurable transforms in between, and simple start/stop methods to control time-based animation execution.
Animated
The Animated library is designed to make animations fluid, powerful, and painless to build and maintain. Animated focuses on declarative relationships between inputs and outputs, with configurable transforms in between, and start/stop methods to control time-based animation execution.
The simplest workflow for creating an animation is to to create an Animated.Value, hook it up to one or more style attributes of an animated component, and then drive updates via animations using Animated.timing():
Animated.timing(
// Animate value over time
@@ -90,7 +90,7 @@
Animated provides three types of animation types. Each animation type provides a particular animation curve that controls how your values animate from their initial value to the final value:
Animated.decay() starts with an initial velocity and gradually slows to a stop.Animated.spring() provides a simple spring physics model.Animated.spring() provides a basic spring physics model.Animated.timing() animates a value over time using easing functions.
In most cases, you will be using timing(). By default, it uses a symmetric easeInOut curve that conveys the gradual acceleration of an object to full speed and concludes by gradually decelerating to a stop.
@@ -100,7 +100,7 @@
By using the native driver, we send everything about the animation to native before starting the animation, allowing native code to perform the animation on the UI thread without having to go through the bridge on every frame. Once the animation has started, the JS thread can be blocked without affecting the animation.
You can use the native driver by specifying useNativeDriver: true in your animation configuration. See the Animations guide to learn more.
Animatable components
-Only animatable components can be animated. These special components do the magic of binding the animated values to the properties, and do targeted native updates to avoid the cost of the react render and reconciliation process on every frame. They also handle cleanup on unmount so they are safe by default.
+Only animatable components can be animated. These components do the magic of binding the animated values to the properties, and do targeted native updates to avoid the cost of the react render and reconciliation process on every frame. They also handle cleanup on unmount so they are safe by default.
createAnimatedComponent() can be used to make a component animatable.
@@ -119,7 +119,7 @@
Animated.sequence() starts the animations in order, waiting for each to complete before starting the next.Animated.stagger() starts animations in order and in parallel, but with successive delays.Animations can also be chained together simply by setting the toValue of one animation to be another Animated.Value. See Tracking dynamic values in the Animations guide.
+Animations can also be chained together by setting the toValue of one animation to be another Animated.Value. See Tracking dynamic values in the Animations guide.
By default, if one animation is stopped or interrupted, then all other animations in the group are also stopped.
Combining animated values
You can combine two animated values via addition, multiplication, division, or modulo to make a new animated value:
diff --git a/docs/0.46/animated/index.html b/docs/0.46/animated/index.html
index ffdf2642632..2c4891ab284 100644
--- a/docs/0.46/animated/index.html
+++ b/docs/0.46/animated/index.html
@@ -1,4 +1,4 @@
-Animated · React Native Animated
The Animated library is designed to make animations fluid, powerful, and easy to build and maintain. Animated focuses on declarative relationships between inputs and outputs, with configurable transforms in between, and simple start/stop methods to control time-based animation execution.
Animated
The Animated library is designed to make animations fluid, powerful, and painless to build and maintain. Animated focuses on declarative relationships between inputs and outputs, with configurable transforms in between, and start/stop methods to control time-based animation execution.
The simplest workflow for creating an animation is to to create an Animated.Value, hook it up to one or more style attributes of an animated component, and then drive updates via animations using Animated.timing():
Animated.timing(
// Animate value over time
@@ -90,7 +90,7 @@
Animated provides three types of animation types. Each animation type provides a particular animation curve that controls how your values animate from their initial value to the final value:
Animated.decay() starts with an initial velocity and gradually slows to a stop.Animated.spring() provides a simple spring physics model.Animated.spring() provides a basic spring physics model.Animated.timing() animates a value over time using easing functions.
In most cases, you will be using timing(). By default, it uses a symmetric easeInOut curve that conveys the gradual acceleration of an object to full speed and concludes by gradually decelerating to a stop.
@@ -100,7 +100,7 @@
By using the native driver, we send everything about the animation to native before starting the animation, allowing native code to perform the animation on the UI thread without having to go through the bridge on every frame. Once the animation has started, the JS thread can be blocked without affecting the animation.
You can use the native driver by specifying useNativeDriver: true in your animation configuration. See the Animations guide to learn more.
Animatable components
-Only animatable components can be animated. These special components do the magic of binding the animated values to the properties, and do targeted native updates to avoid the cost of the react render and reconciliation process on every frame. They also handle cleanup on unmount so they are safe by default.
+Only animatable components can be animated. These components do the magic of binding the animated values to the properties, and do targeted native updates to avoid the cost of the react render and reconciliation process on every frame. They also handle cleanup on unmount so they are safe by default.
createAnimatedComponent() can be used to make a component animatable.
@@ -119,7 +119,7 @@
Animated.sequence() starts the animations in order, waiting for each to complete before starting the next.Animated.stagger() starts animations in order and in parallel, but with successive delays.Animations can also be chained together simply by setting the toValue of one animation to be another Animated.Value. See Tracking dynamic values in the Animations guide.
+Animations can also be chained together by setting the toValue of one animation to be another Animated.Value. See Tracking dynamic values in the Animations guide.
By default, if one animation is stopped or interrupted, then all other animations in the group are also stopped.
Combining animated values
You can combine two animated values via addition, multiplication, division, or modulo to make a new animated value:
diff --git a/docs/0.46/appstate.html b/docs/0.46/appstate.html
index 6e72d17e951..8d1b7ef166f 100644
--- a/docs/0.46/appstate.html
+++ b/docs/0.46/appstate.html
@@ -138,7 +138,7 @@
handler function Yes TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and just use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
+TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
removeEventListener()
removeEventListener(type, handler);
diff --git a/docs/0.46/appstate/index.html b/docs/0.46/appstate/index.html
index 6e72d17e951..8d1b7ef166f 100644
--- a/docs/0.46/appstate/index.html
+++ b/docs/0.46/appstate/index.html
@@ -138,7 +138,7 @@
handler function Yes TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and just use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
+TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
removeEventListener()
removeEventListener(type, handler);
diff --git a/docs/0.46/flatlist.html b/docs/0.46/flatlist.html
index 8e736177639..b40aebbb3b2 100644
--- a/docs/0.46/flatlist.html
+++ b/docs/0.46/flatlist.html
@@ -1,4 +1,4 @@
-FlatList · React Native
FlatList
A performant interface for rendering simple, flat lists, supporting the most handy features:
+FlatList
A performant interface for rendering flat lists supporting the most handy features:
- Fully cross-platform.
- Optional horizontal mode. @@ -200,7 +200,7 @@ class MyList extends React.PureComponent {
data
-For simplicity, data is just a plain array. If you want to use something else, like an immutable list, use the underlying VirtualizedList directly.
For simplicity, data is a plain array. If you want to use something else, like an immutable list, use the underlying VirtualizedList directly.
| Type | Required |
|---|
getItemLayout
-getItemLayout is an optional optimizations that let us skip measurement of dynamic content if you know the height of items a priori. getItemLayout is the most efficient, and is easy to use if you have fixed height items, for example:
getItemLayout is an optional optimizations that let us skip measurement of dynamic content if you know the height of items a priori. getItemLayout is the most efficient if you have fixed height items, for example:
getItemLayout={(data, index) => (
{length: ITEM_HEIGHT, offset: ITEM_HEIGHT * index, index}
)}
diff --git a/docs/0.46/flatlist/index.html b/docs/0.46/flatlist/index.html
index 8e736177639..b40aebbb3b2 100644
--- a/docs/0.46/flatlist/index.html
+++ b/docs/0.46/flatlist/index.html
@@ -1,4 +1,4 @@
-FlatList · React Native FlatList
A performant interface for rendering simple, flat lists, supporting the most handy features:
+FlatList
A performant interface for rendering flat lists supporting the most handy features:
- Fully cross-platform.
- Optional horizontal mode. @@ -200,7 +200,7 @@ class MyList extends React.PureComponent {
data
-For simplicity, data is just a plain array. If you want to use something else, like an immutable list, use the underlying VirtualizedList directly.
For simplicity, data is a plain array. If you want to use something else, like an immutable list, use the underlying VirtualizedList directly.
| Type | Required |
|---|
getItemLayout
-getItemLayout is an optional optimizations that let us skip measurement of dynamic content if you know the height of items a priori. getItemLayout is the most efficient, and is easy to use if you have fixed height items, for example:
getItemLayout is an optional optimizations that let us skip measurement of dynamic content if you know the height of items a priori. getItemLayout is the most efficient if you have fixed height items, for example:
getItemLayout={(data, index) => (
{length: ITEM_HEIGHT, offset: ITEM_HEIGHT * index, index}
)}
diff --git a/docs/0.46/imagebackground.html b/docs/0.46/imagebackground.html
index dfecace3fd7..0ef2378b303 100644
--- a/docs/0.46/imagebackground.html
+++ b/docs/0.46/imagebackground.html
@@ -69,7 +69,7 @@
}
});
ImageBackground
A common feature request from developers familiar with the web is background-image. To handle this use case, you can use the <ImageBackground> component, which has the same props as <Image>, and add whatever children to it you would like to layer on top of it.
You might not want to use <ImageBackground> in some cases, since the implementation is very simple. Refer to <ImageBackground>'s source code for more insight, and create your own custom component when needed.
You might not want to use <ImageBackground> in some cases, since the implementation is very basic. Refer to <ImageBackground>'s source code for more insight, and create your own custom component when needed.
Note that you must specify some width and height style attributes.
Example
return (
diff --git a/docs/0.46/imagebackground/index.html b/docs/0.46/imagebackground/index.html
index dfecace3fd7..0ef2378b303 100644
--- a/docs/0.46/imagebackground/index.html
+++ b/docs/0.46/imagebackground/index.html
@@ -69,7 +69,7 @@
}
});
ImageBackground
A common feature request from developers familiar with the web is background-image. To handle this use case, you can use the <ImageBackground> component, which has the same props as <Image>, and add whatever children to it you would like to layer on top of it.
You might not want to use <ImageBackground> in some cases, since the implementation is very simple. Refer to <ImageBackground>'s source code for more insight, and create your own custom component when needed.
You might not want to use <ImageBackground> in some cases, since the implementation is very basic. Refer to <ImageBackground>'s source code for more insight, and create your own custom component when needed.
Note that you must specify some width and height style attributes.
Example
return (
diff --git a/docs/0.46/layout-props.html b/docs/0.46/layout-props.html
index 155b1d92286..df091743a74 100644
--- a/docs/0.46/layout-props.html
+++ b/docs/0.46/layout-props.html
@@ -571,9 +571,9 @@
position
-position in React Native is similar to regular CSS, but everything is set to relative by default, so absolute positioning is always just relative to the parent.
+position in React Native is similar to regular CSS, but everything is set to relative by default, so absolute positioning is always relative to the parent.
If you want to position a child using specific numbers of logical pixels relative to its parent, set the child to have absolute position.
-If you want to position a child relative to something that is not its parent, just don't use styles for that. Use the component tree.
+If you want to position a child relative to something that is not its parent, don't use styles for that. Use the component tree.
See https://github.com/facebook/yoga for more details on how position differs between React Native and CSS.
diff --git a/docs/0.46/layout-props/index.html b/docs/0.46/layout-props/index.html
index 155b1d92286..df091743a74 100644
--- a/docs/0.46/layout-props/index.html
+++ b/docs/0.46/layout-props/index.html
@@ -571,9 +571,9 @@
position
-position in React Native is similar to regular CSS, but everything is set to relative by default, so absolute positioning is always just relative to the parent.
+position in React Native is similar to regular CSS, but everything is set to relative by default, so absolute positioning is always relative to the parent.
If you want to position a child using specific numbers of logical pixels relative to its parent, set the child to have absolute position.
-If you want to position a child relative to something that is not its parent, just don't use styles for that. Use the component tree.
+If you want to position a child relative to something that is not its parent, don't use styles for that. Use the component tree.
See https://github.com/facebook/yoga for more details on how position differs between React Native and CSS.
diff --git a/docs/0.46/listview.html b/docs/0.46/listview.html
index 1e8b94c6fc3..792e157121c 100644
--- a/docs/0.46/listview.html
+++ b/docs/0.46/listview.html
@@ -1,4 +1,4 @@
-ListView · React Native EditListView
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 callback which takes a blob from the data array and returns a renderable component.
+ EditListView
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 array of data blobs, and instantiate a ListView component with that data source and a renderRow callback which takes a blob from the data array and returns a renderable component.
Minimal example:
class MyComponent extends Component {
constructor() {
diff --git a/docs/0.46/listview/index.html b/docs/0.46/listview/index.html
index 1e8b94c6fc3..792e157121c 100644
--- a/docs/0.46/listview/index.html
+++ b/docs/0.46/listview/index.html
@@ -1,4 +1,4 @@
-ListView · React Native
EditListView
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 callback which takes a blob from the data array and returns a renderable component.
+ EditListView
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 array of data blobs, and instantiate a ListView component with that data source and a renderRow callback which takes a blob from the data array and returns a renderable component.
Minimal example:
class MyComponent extends Component {
constructor() {
diff --git a/docs/0.46/scrollview.html b/docs/0.46/scrollview.html
index e65794be541..8cd9e2175cd 100644
--- a/docs/0.46/scrollview.html
+++ b/docs/0.46/scrollview.html
@@ -69,12 +69,12 @@
}
});
EditScrollView
Component that wraps platform ScrollView while providing integration with touch locking "responder" system.
-Keep in mind that ScrollViews must have a bounded height in order to work, since they contain unbounded-height children into a bounded container (via a scroll interaction). In order to bound the height of a ScrollView, either set the height of the view directly (discouraged) or make sure all parent views have bounded height. Forgetting to transfer {flex: 1} down the view stack can lead to errors here, which the element inspector makes easy to debug.
+Keep in mind that ScrollViews must have a bounded height in order to work, since they contain unbounded-height children into a bounded container (via a scroll interaction). In order to bound the height of a ScrollView, either set the height of the view directly (discouraged) or make sure all parent views have bounded height. Forgetting to transfer {flex: 1} down the view stack can lead to errors here, which the element inspector makes quick to debug.
Doesn't yet support other contained responders from blocking this scroll view from becoming the responder.
<ScrollView> vs <FlatList> - which one to use?
-ScrollView simply renders all its react child components at once. That makes it very easy to understand and use.
+ScrollView renders all its react child components at once. That enables us to understand and use them in brief.
On the other hand, this has a performance downside. Imagine you have a very long list of items you want to display, maybe several screens worth of content. Creating JS components and native views for everything all at once, much of which may not even be shown, will contribute to slow rendering and increased memory usage.
-This is where FlatList comes into play. FlatList renders items lazily, just when they are about to appear, and removes items that scroll way off screen to save memory and processing time.
+This is where FlatList comes into play. FlatList renders items lazily, when they are about to appear, and removes items that scroll way off screen to save memory and processing time.
FlatList is also handy if you want to render separators between your items, multiple columns, infinite scroll loading, or any number of other features it supports out of the box.
Props
@@ -504,8 +504,8 @@ const styles = StyleSheet.create({
The style of the scroll indicators.
'default' (the default), same as black.'black', scroll indicator is black. This style is good against a light background.'white', scroll indicator is white. This style is good against a dark background.'black', scroll indicator is black. This style is good against a light background.'white', scroll indicator is white. This style is good against a dark background.
diff --git a/docs/0.46/scrollview/index.html b/docs/0.46/scrollview/index.html
index e65794be541..8cd9e2175cd 100644
--- a/docs/0.46/scrollview/index.html
+++ b/docs/0.46/scrollview/index.html
@@ -69,12 +69,12 @@
}
});
EditScrollView
Component that wraps platform ScrollView while providing integration with touch locking "responder" system.
-Keep in mind that ScrollViews must have a bounded height in order to work, since they contain unbounded-height children into a bounded container (via a scroll interaction). In order to bound the height of a ScrollView, either set the height of the view directly (discouraged) or make sure all parent views have bounded height. Forgetting to transfer {flex: 1} down the view stack can lead to errors here, which the element inspector makes easy to debug.
+Keep in mind that ScrollViews must have a bounded height in order to work, since they contain unbounded-height children into a bounded container (via a scroll interaction). In order to bound the height of a ScrollView, either set the height of the view directly (discouraged) or make sure all parent views have bounded height. Forgetting to transfer {flex: 1} down the view stack can lead to errors here, which the element inspector makes quick to debug.
Doesn't yet support other contained responders from blocking this scroll view from becoming the responder.
<ScrollView> vs <FlatList> - which one to use?
-ScrollView simply renders all its react child components at once. That makes it very easy to understand and use.
+ScrollView renders all its react child components at once. That enables us to understand and use them in brief.
On the other hand, this has a performance downside. Imagine you have a very long list of items you want to display, maybe several screens worth of content. Creating JS components and native views for everything all at once, much of which may not even be shown, will contribute to slow rendering and increased memory usage.
-This is where FlatList comes into play. FlatList renders items lazily, just when they are about to appear, and removes items that scroll way off screen to save memory and processing time.
+This is where FlatList comes into play. FlatList renders items lazily, when they are about to appear, and removes items that scroll way off screen to save memory and processing time.
FlatList is also handy if you want to render separators between your items, multiple columns, infinite scroll loading, or any number of other features it supports out of the box.
Props
@@ -504,8 +504,8 @@ const styles = StyleSheet.create({
The style of the scroll indicators.
'default' (the default), same as black.'black', scroll indicator is black. This style is good against a light background.'white', scroll indicator is white. This style is good against a dark background.'black', scroll indicator is black. This style is good against a light background.'white', scroll indicator is white. This style is good against a dark background.
diff --git a/docs/0.46/sectionlist.html b/docs/0.46/sectionlist.html
index cdf770a76d1..7e1f5c29871 100644
--- a/docs/0.46/sectionlist.html
+++ b/docs/0.46/sectionlist.html
@@ -82,7 +82,7 @@
- Scroll loading.
If you don't need section support and want a simpler interface, use <FlatList>.
-Simple Examples:
+Examples:
<SectionList
renderItem={({item}) => <ListItem title={item.title} />}
renderSectionHeader={({section}) => <H1 title={section.title} />}
diff --git a/docs/0.46/sectionlist/index.html b/docs/0.46/sectionlist/index.html
index cdf770a76d1..7e1f5c29871 100644
--- a/docs/0.46/sectionlist/index.html
+++ b/docs/0.46/sectionlist/index.html
@@ -82,7 +82,7 @@
- Scroll loading.
If you don't need section support and want a simpler interface, use <FlatList>.
-Simple Examples:
+Examples:
<SectionList
renderItem={({item}) => <ListItem title={item.title} />}
renderSectionHeader={({section}) => <H1 title={section.title} />}
diff --git a/docs/0.47/animated.html b/docs/0.47/animated.html
index 373a4b6ad2e..f2c6cc8920e 100644
--- a/docs/0.47/animated.html
+++ b/docs/0.47/animated.html
@@ -1,4 +1,4 @@
-Animated · React Native EditAnimated
The Animated library is designed to make animations fluid, powerful, and easy to build and maintain. Animated focuses on declarative relationships between inputs and outputs, with configurable transforms in between, and simple start/stop methods to control time-based animation execution.
+ EditAnimated
The Animated library is designed to make animations fluid, powerful, and painless to build and maintain. Animated focuses on declarative relationships between inputs and outputs, with configurable transforms in between, and start/stop methods to control time-based animation execution.
The simplest workflow for creating an animation is to to create an Animated.Value, hook it up to one or more style attributes of an animated component, and then drive updates via animations using Animated.timing():
Animated.timing(
// Animate value over time
@@ -90,7 +90,7 @@
Animated provides three types of animation types. Each animation type provides a particular animation curve that controls how your values animate from their initial value to the final value:
Animated.decay() starts with an initial velocity and gradually slows to a stop.Animated.spring() provides a simple spring physics model.Animated.spring() provides a basic spring physics model.Animated.timing() animates a value over time using easing functions.
In most cases, you will be using timing(). By default, it uses a symmetric easeInOut curve that conveys the gradual acceleration of an object to full speed and concludes by gradually decelerating to a stop.
@@ -100,7 +100,7 @@
By using the native driver, we send everything about the animation to native before starting the animation, allowing native code to perform the animation on the UI thread without having to go through the bridge on every frame. Once the animation has started, the JS thread can be blocked without affecting the animation.
You can use the native driver by specifying useNativeDriver: true in your animation configuration. See the Animations guide to learn more.
Animatable components
-Only animatable components can be animated. These special components do the magic of binding the animated values to the properties, and do targeted native updates to avoid the cost of the react render and reconciliation process on every frame. They also handle cleanup on unmount so they are safe by default.
+Only animatable components can be animated. These components do the magic of binding the animated values to the properties, and do targeted native updates to avoid the cost of the react render and reconciliation process on every frame. They also handle cleanup on unmount so they are safe by default.
createAnimatedComponent() can be used to make a component animatable.
@@ -119,7 +119,7 @@
Animated.sequence() starts the animations in order, waiting for each to complete before starting the next.Animated.stagger() starts animations in order and in parallel, but with successive delays.Animations can also be chained together simply by setting the toValue of one animation to be another Animated.Value. See Tracking dynamic values in the Animations guide.
+Animations can also be chained together by setting the toValue of one animation to be another Animated.Value. See Tracking dynamic values in the Animations guide.
By default, if one animation is stopped or interrupted, then all other animations in the group are also stopped.
Combining animated values
You can combine two animated values via addition, multiplication, division, or modulo to make a new animated value:
diff --git a/docs/0.47/animated/index.html b/docs/0.47/animated/index.html
index 373a4b6ad2e..f2c6cc8920e 100644
--- a/docs/0.47/animated/index.html
+++ b/docs/0.47/animated/index.html
@@ -1,4 +1,4 @@
-Animated · React Native
EditAnimated
The Animated library is designed to make animations fluid, powerful, and easy to build and maintain. Animated focuses on declarative relationships between inputs and outputs, with configurable transforms in between, and simple start/stop methods to control time-based animation execution.
+ EditAnimated
The Animated library is designed to make animations fluid, powerful, and painless to build and maintain. Animated focuses on declarative relationships between inputs and outputs, with configurable transforms in between, and start/stop methods to control time-based animation execution.
The simplest workflow for creating an animation is to to create an Animated.Value, hook it up to one or more style attributes of an animated component, and then drive updates via animations using Animated.timing():
Animated.timing(
// Animate value over time
@@ -90,7 +90,7 @@
Animated provides three types of animation types. Each animation type provides a particular animation curve that controls how your values animate from their initial value to the final value:
Animated.decay() starts with an initial velocity and gradually slows to a stop.Animated.spring() provides a simple spring physics model.Animated.spring() provides a basic spring physics model.Animated.timing() animates a value over time using easing functions.
In most cases, you will be using timing(). By default, it uses a symmetric easeInOut curve that conveys the gradual acceleration of an object to full speed and concludes by gradually decelerating to a stop.
@@ -100,7 +100,7 @@
By using the native driver, we send everything about the animation to native before starting the animation, allowing native code to perform the animation on the UI thread without having to go through the bridge on every frame. Once the animation has started, the JS thread can be blocked without affecting the animation.
You can use the native driver by specifying useNativeDriver: true in your animation configuration. See the Animations guide to learn more.
Animatable components
-Only animatable components can be animated. These special components do the magic of binding the animated values to the properties, and do targeted native updates to avoid the cost of the react render and reconciliation process on every frame. They also handle cleanup on unmount so they are safe by default.
+Only animatable components can be animated. These components do the magic of binding the animated values to the properties, and do targeted native updates to avoid the cost of the react render and reconciliation process on every frame. They also handle cleanup on unmount so they are safe by default.
createAnimatedComponent() can be used to make a component animatable.
@@ -119,7 +119,7 @@
Animated.sequence() starts the animations in order, waiting for each to complete before starting the next.Animated.stagger() starts animations in order and in parallel, but with successive delays.Animations can also be chained together simply by setting the toValue of one animation to be another Animated.Value. See Tracking dynamic values in the Animations guide.
+Animations can also be chained together by setting the toValue of one animation to be another Animated.Value. See Tracking dynamic values in the Animations guide.
By default, if one animation is stopped or interrupted, then all other animations in the group are also stopped.
Combining animated values
You can combine two animated values via addition, multiplication, division, or modulo to make a new animated value:
diff --git a/docs/0.47/appstate.html b/docs/0.47/appstate.html
index fb4222fa571..20a60e563bf 100644
--- a/docs/0.47/appstate.html
+++ b/docs/0.47/appstate.html
@@ -138,7 +138,7 @@
handler function Yes
-TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and just use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
+TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
removeEventListener()
removeEventListener(type, handler);
diff --git a/docs/0.47/appstate/index.html b/docs/0.47/appstate/index.html
index fb4222fa571..20a60e563bf 100644
--- a/docs/0.47/appstate/index.html
+++ b/docs/0.47/appstate/index.html
@@ -138,7 +138,7 @@
handler function Yes
-TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and just use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
+TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
removeEventListener()
removeEventListener(type, handler);
diff --git a/docs/0.47/imagebackground.html b/docs/0.47/imagebackground.html
index da328c298e2..5ac92681a1a 100644
--- a/docs/0.47/imagebackground.html
+++ b/docs/0.47/imagebackground.html
@@ -69,7 +69,7 @@
}
});
EditImageBackground
A common feature request from developers familiar with the web is background-image. To handle this use case, you can use the <ImageBackground> component, which has the same props as <Image>, and add whatever children to it you would like to layer on top of it.
-You might not want to use <ImageBackground> in some cases, since the implementation is very simple. Refer to <ImageBackground>'s source code for more insight, and create your own custom component when needed.
+You might not want to use <ImageBackground> in some cases, since the implementation is very basic. Refer to <ImageBackground>'s source code for more insight, and create your own custom component when needed.
Note that you must specify some width and height style attributes.
Example
return (
diff --git a/docs/0.47/imagebackground/index.html b/docs/0.47/imagebackground/index.html
index da328c298e2..5ac92681a1a 100644
--- a/docs/0.47/imagebackground/index.html
+++ b/docs/0.47/imagebackground/index.html
@@ -69,7 +69,7 @@
}
});
EditImageBackground
A common feature request from developers familiar with the web is background-image. To handle this use case, you can use the <ImageBackground> component, which has the same props as <Image>, and add whatever children to it you would like to layer on top of it.
-You might not want to use <ImageBackground> in some cases, since the implementation is very simple. Refer to <ImageBackground>'s source code for more insight, and create your own custom component when needed.
+You might not want to use <ImageBackground> in some cases, since the implementation is very basic. Refer to <ImageBackground>'s source code for more insight, and create your own custom component when needed.
Note that you must specify some width and height style attributes.
Example
return (
diff --git a/docs/0.47/listview.html b/docs/0.47/listview.html
index 562bec7faa2..665e3d5477a 100644
--- a/docs/0.47/listview.html
+++ b/docs/0.47/listview.html
@@ -1,4 +1,4 @@
-ListView · React Native
EditListView
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 callback which takes a blob from the data array and returns a renderable component.
+ EditListView
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 array of data blobs, and instantiate a ListView component with that data source and a renderRow callback which takes a blob from the data array and returns a renderable component.
Minimal example:
class MyComponent extends Component {
constructor() {
diff --git a/docs/0.47/listview/index.html b/docs/0.47/listview/index.html
index 562bec7faa2..665e3d5477a 100644
--- a/docs/0.47/listview/index.html
+++ b/docs/0.47/listview/index.html
@@ -1,4 +1,4 @@
-ListView · React Native
EditListView
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 callback which takes a blob from the data array and returns a renderable component.
+ EditListView
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 array of data blobs, and instantiate a ListView component with that data source and a renderRow callback which takes a blob from the data array and returns a renderable component.
Minimal example:
class MyComponent extends Component {
constructor() {
diff --git a/docs/0.48/appstate.html b/docs/0.48/appstate.html
index 50a15dc2736..1becda1d3cd 100644
--- a/docs/0.48/appstate.html
+++ b/docs/0.48/appstate.html
@@ -138,7 +138,7 @@
handler function Yes
-TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and just use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
+TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
removeEventListener()
removeEventListener(type, handler);
diff --git a/docs/0.48/appstate/index.html b/docs/0.48/appstate/index.html
index 50a15dc2736..1becda1d3cd 100644
--- a/docs/0.48/appstate/index.html
+++ b/docs/0.48/appstate/index.html
@@ -138,7 +138,7 @@
handler function Yes TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and just use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
+TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
removeEventListener()
removeEventListener(type, handler);
diff --git a/docs/0.48/imagebackground.html b/docs/0.48/imagebackground.html
index 8b4a9049b1a..e65fa511252 100644
--- a/docs/0.48/imagebackground.html
+++ b/docs/0.48/imagebackground.html
@@ -69,7 +69,7 @@
}
});
ImageBackground
A common feature request from developers familiar with the web is background-image. To handle this use case, you can use the <ImageBackground> component, which has the same props as <Image>, and add whatever children to it you would like to layer on top of it.
You might not want to use <ImageBackground> in some cases, since the implementation is very simple. Refer to <ImageBackground>'s source code for more insight, and create your own custom component when needed.
You might not want to use <ImageBackground> in some cases, since the implementation is very basic. Refer to <ImageBackground>'s source code for more insight, and create your own custom component when needed.
Note that you must specify some width and height style attributes.
Example
return (
diff --git a/docs/0.48/imagebackground/index.html b/docs/0.48/imagebackground/index.html
index 8b4a9049b1a..e65fa511252 100644
--- a/docs/0.48/imagebackground/index.html
+++ b/docs/0.48/imagebackground/index.html
@@ -69,7 +69,7 @@
}
});
ImageBackground
A common feature request from developers familiar with the web is background-image. To handle this use case, you can use the <ImageBackground> component, which has the same props as <Image>, and add whatever children to it you would like to layer on top of it.
You might not want to use <ImageBackground> in some cases, since the implementation is very simple. Refer to <ImageBackground>'s source code for more insight, and create your own custom component when needed.
You might not want to use <ImageBackground> in some cases, since the implementation is very basic. Refer to <ImageBackground>'s source code for more insight, and create your own custom component when needed.
Note that you must specify some width and height style attributes.
Example
return (
diff --git a/docs/0.49/appstate.html b/docs/0.49/appstate.html
index 5908343bd06..b3a07210930 100644
--- a/docs/0.49/appstate.html
+++ b/docs/0.49/appstate.html
@@ -138,7 +138,7 @@
handler function Yes TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and just use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
+TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
removeEventListener()
removeEventListener(type, handler);
diff --git a/docs/0.49/appstate/index.html b/docs/0.49/appstate/index.html
index 5908343bd06..b3a07210930 100644
--- a/docs/0.49/appstate/index.html
+++ b/docs/0.49/appstate/index.html
@@ -138,7 +138,7 @@
handler function Yes TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and just use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
+TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
removeEventListener()
removeEventListener(type, handler);
diff --git a/docs/0.49/imagebackground.html b/docs/0.49/imagebackground.html
index daff519d7bf..5da9e495b38 100644
--- a/docs/0.49/imagebackground.html
+++ b/docs/0.49/imagebackground.html
@@ -69,7 +69,7 @@
}
});
ImageBackground
A common feature request from developers familiar with the web is background-image. To handle this use case, you can use the <ImageBackground> component, which has the same props as <Image>, and add whatever children to it you would like to layer on top of it.
You might not want to use <ImageBackground> in some cases, since the implementation is very simple. Refer to <ImageBackground>'s source code for more insight, and create your own custom component when needed.
You might not want to use <ImageBackground> in some cases, since the implementation is very basic. Refer to <ImageBackground>'s source code for more insight, and create your own custom component when needed.
Note that you must specify some width and height style attributes.
Example
return (
diff --git a/docs/0.49/imagebackground/index.html b/docs/0.49/imagebackground/index.html
index daff519d7bf..5da9e495b38 100644
--- a/docs/0.49/imagebackground/index.html
+++ b/docs/0.49/imagebackground/index.html
@@ -69,7 +69,7 @@
}
});
ImageBackground
A common feature request from developers familiar with the web is background-image. To handle this use case, you can use the <ImageBackground> component, which has the same props as <Image>, and add whatever children to it you would like to layer on top of it.
You might not want to use <ImageBackground> in some cases, since the implementation is very simple. Refer to <ImageBackground>'s source code for more insight, and create your own custom component when needed.
You might not want to use <ImageBackground> in some cases, since the implementation is very basic. Refer to <ImageBackground>'s source code for more insight, and create your own custom component when needed.
Note that you must specify some width and height style attributes.
Example
return (
diff --git a/docs/0.50/appstate.html b/docs/0.50/appstate.html
index 4676406d027..58a72adeab7 100644
--- a/docs/0.50/appstate.html
+++ b/docs/0.50/appstate.html
@@ -138,7 +138,7 @@
handler function Yes TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and just use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
+TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
removeEventListener()
removeEventListener(type, handler);
diff --git a/docs/0.50/appstate/index.html b/docs/0.50/appstate/index.html
index 4676406d027..58a72adeab7 100644
--- a/docs/0.50/appstate/index.html
+++ b/docs/0.50/appstate/index.html
@@ -138,7 +138,7 @@
handler function Yes TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and just use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
+TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
removeEventListener()
removeEventListener(type, handler);
diff --git a/docs/0.50/imagebackground.html b/docs/0.50/imagebackground.html
index c78a08b1900..195360e7cc2 100644
--- a/docs/0.50/imagebackground.html
+++ b/docs/0.50/imagebackground.html
@@ -69,7 +69,7 @@
}
});
ImageBackground
A common feature request from developers familiar with the web is background-image. To handle this use case, you can use the <ImageBackground> component, which has the same props as <Image>, and add whatever children to it you would like to layer on top of it.
You might not want to use <ImageBackground> in some cases, since the implementation is very simple. Refer to <ImageBackground>'s source code for more insight, and create your own custom component when needed.
You might not want to use <ImageBackground> in some cases, since the implementation is very basic. Refer to <ImageBackground>'s source code for more insight, and create your own custom component when needed.
Note that you must specify some width and height style attributes.
Example
return (
diff --git a/docs/0.50/imagebackground/index.html b/docs/0.50/imagebackground/index.html
index c78a08b1900..195360e7cc2 100644
--- a/docs/0.50/imagebackground/index.html
+++ b/docs/0.50/imagebackground/index.html
@@ -69,7 +69,7 @@
}
});
ImageBackground
A common feature request from developers familiar with the web is background-image. To handle this use case, you can use the <ImageBackground> component, which has the same props as <Image>, and add whatever children to it you would like to layer on top of it.
You might not want to use <ImageBackground> in some cases, since the implementation is very simple. Refer to <ImageBackground>'s source code for more insight, and create your own custom component when needed.
You might not want to use <ImageBackground> in some cases, since the implementation is very basic. Refer to <ImageBackground>'s source code for more insight, and create your own custom component when needed.
Note that you must specify some width and height style attributes.
Example
return (
diff --git a/docs/0.51/appstate.html b/docs/0.51/appstate.html
index 6035dfb989e..c377a347aa5 100644
--- a/docs/0.51/appstate.html
+++ b/docs/0.51/appstate.html
@@ -138,7 +138,7 @@
handler function Yes TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and just use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
+TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
removeEventListener()
removeEventListener(type, handler);
diff --git a/docs/0.51/appstate/index.html b/docs/0.51/appstate/index.html
index 6035dfb989e..c377a347aa5 100644
--- a/docs/0.51/appstate/index.html
+++ b/docs/0.51/appstate/index.html
@@ -138,7 +138,7 @@
handler function Yes TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and just use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
+TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
removeEventListener()
removeEventListener(type, handler);
diff --git a/docs/0.51/imagebackground.html b/docs/0.51/imagebackground.html
index 9cb37a68e7d..4f91826a106 100644
--- a/docs/0.51/imagebackground.html
+++ b/docs/0.51/imagebackground.html
@@ -69,7 +69,7 @@
}
});
ImageBackground
A common feature request from developers familiar with the web is background-image. To handle this use case, you can use the <ImageBackground> component, which has the same props as <Image>, and add whatever children to it you would like to layer on top of it.
You might not want to use <ImageBackground> in some cases, since the implementation is very simple. Refer to <ImageBackground>'s source code for more insight, and create your own custom component when needed.
You might not want to use <ImageBackground> in some cases, since the implementation is very basic. Refer to <ImageBackground>'s source code for more insight, and create your own custom component when needed.
Note that you must specify some width and height style attributes.
Example
return (
diff --git a/docs/0.51/imagebackground/index.html b/docs/0.51/imagebackground/index.html
index 9cb37a68e7d..4f91826a106 100644
--- a/docs/0.51/imagebackground/index.html
+++ b/docs/0.51/imagebackground/index.html
@@ -69,7 +69,7 @@
}
});
ImageBackground
A common feature request from developers familiar with the web is background-image. To handle this use case, you can use the <ImageBackground> component, which has the same props as <Image>, and add whatever children to it you would like to layer on top of it.
You might not want to use <ImageBackground> in some cases, since the implementation is very simple. Refer to <ImageBackground>'s source code for more insight, and create your own custom component when needed.
You might not want to use <ImageBackground> in some cases, since the implementation is very basic. Refer to <ImageBackground>'s source code for more insight, and create your own custom component when needed.
Note that you must specify some width and height style attributes.
Example
return (
diff --git a/docs/0.52/appstate.html b/docs/0.52/appstate.html
index 3ab894bb296..7839b348932 100644
--- a/docs/0.52/appstate.html
+++ b/docs/0.52/appstate.html
@@ -138,7 +138,7 @@
handler function Yes TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and just use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
+TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
removeEventListener()
removeEventListener(type, handler);
diff --git a/docs/0.52/appstate/index.html b/docs/0.52/appstate/index.html
index 3ab894bb296..7839b348932 100644
--- a/docs/0.52/appstate/index.html
+++ b/docs/0.52/appstate/index.html
@@ -138,7 +138,7 @@
handler function Yes TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and just use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
+TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
removeEventListener()
removeEventListener(type, handler);
diff --git a/docs/0.52/imagebackground.html b/docs/0.52/imagebackground.html
index e69f8d1ad9f..dc695ffd12e 100644
--- a/docs/0.52/imagebackground.html
+++ b/docs/0.52/imagebackground.html
@@ -69,7 +69,7 @@
}
});
ImageBackground
A common feature request from developers familiar with the web is background-image. To handle this use case, you can use the <ImageBackground> component, which has the same props as <Image>, and add whatever children to it you would like to layer on top of it.
You might not want to use <ImageBackground> in some cases, since the implementation is very simple. Refer to <ImageBackground>'s source code for more insight, and create your own custom component when needed.
You might not want to use <ImageBackground> in some cases, since the implementation is very basic. Refer to <ImageBackground>'s source code for more insight, and create your own custom component when needed.
Note that you must specify some width and height style attributes.
Example
return (
diff --git a/docs/0.52/imagebackground/index.html b/docs/0.52/imagebackground/index.html
index e69f8d1ad9f..dc695ffd12e 100644
--- a/docs/0.52/imagebackground/index.html
+++ b/docs/0.52/imagebackground/index.html
@@ -69,7 +69,7 @@
}
});
ImageBackground
A common feature request from developers familiar with the web is background-image. To handle this use case, you can use the <ImageBackground> component, which has the same props as <Image>, and add whatever children to it you would like to layer on top of it.
You might not want to use <ImageBackground> in some cases, since the implementation is very simple. Refer to <ImageBackground>'s source code for more insight, and create your own custom component when needed.
You might not want to use <ImageBackground> in some cases, since the implementation is very basic. Refer to <ImageBackground>'s source code for more insight, and create your own custom component when needed.
Note that you must specify some width and height style attributes.
Example
return (
diff --git a/docs/0.53/imagebackground.html b/docs/0.53/imagebackground.html
index cdcda66adea..ab5fac2cb49 100644
--- a/docs/0.53/imagebackground.html
+++ b/docs/0.53/imagebackground.html
@@ -69,7 +69,7 @@
}
});
ImageBackground
A common feature request from developers familiar with the web is background-image. To handle this use case, you can use the <ImageBackground> component, which has the same props as <Image>, and add whatever children to it you would like to layer on top of it.
You might not want to use <ImageBackground> in some cases, since the implementation is very simple. Refer to <ImageBackground>'s source code for more insight, and create your own custom component when needed.
You might not want to use <ImageBackground> in some cases, since the implementation is very basic. Refer to <ImageBackground>'s source code for more insight, and create your own custom component when needed.
Note that you must specify some width and height style attributes.
Example
return (
diff --git a/docs/0.53/imagebackground/index.html b/docs/0.53/imagebackground/index.html
index cdcda66adea..ab5fac2cb49 100644
--- a/docs/0.53/imagebackground/index.html
+++ b/docs/0.53/imagebackground/index.html
@@ -69,7 +69,7 @@
}
});
ImageBackground
A common feature request from developers familiar with the web is background-image. To handle this use case, you can use the <ImageBackground> component, which has the same props as <Image>, and add whatever children to it you would like to layer on top of it.
You might not want to use <ImageBackground> in some cases, since the implementation is very simple. Refer to <ImageBackground>'s source code for more insight, and create your own custom component when needed.
You might not want to use <ImageBackground> in some cases, since the implementation is very basic. Refer to <ImageBackground>'s source code for more insight, and create your own custom component when needed.
Note that you must specify some width and height style attributes.
Example
return (
diff --git a/docs/0.54/imagebackground.html b/docs/0.54/imagebackground.html
index 04ded9dbbb9..b78ce6af984 100644
--- a/docs/0.54/imagebackground.html
+++ b/docs/0.54/imagebackground.html
@@ -69,7 +69,7 @@
}
});
ImageBackground
A common feature request from developers familiar with the web is background-image. To handle this use case, you can use the <ImageBackground> component, which has the same props as <Image>, and add whatever children to it you would like to layer on top of it.
You might not want to use <ImageBackground> in some cases, since the implementation is very simple. Refer to <ImageBackground>'s source code for more insight, and create your own custom component when needed.
You might not want to use <ImageBackground> in some cases, since the implementation is very basic. Refer to <ImageBackground>'s source code for more insight, and create your own custom component when needed.
Note that you must specify some width and height style attributes.
Example
return (
diff --git a/docs/0.54/imagebackground/index.html b/docs/0.54/imagebackground/index.html
index 04ded9dbbb9..b78ce6af984 100644
--- a/docs/0.54/imagebackground/index.html
+++ b/docs/0.54/imagebackground/index.html
@@ -69,7 +69,7 @@
}
});
ImageBackground
A common feature request from developers familiar with the web is background-image. To handle this use case, you can use the <ImageBackground> component, which has the same props as <Image>, and add whatever children to it you would like to layer on top of it.
You might not want to use <ImageBackground> in some cases, since the implementation is very simple. Refer to <ImageBackground>'s source code for more insight, and create your own custom component when needed.
You might not want to use <ImageBackground> in some cases, since the implementation is very basic. Refer to <ImageBackground>'s source code for more insight, and create your own custom component when needed.
Note that you must specify some width and height style attributes.
Example
return (
diff --git a/docs/0.55/imagebackground.html b/docs/0.55/imagebackground.html
index f25d6909fa3..d08dbe3c3a6 100644
--- a/docs/0.55/imagebackground.html
+++ b/docs/0.55/imagebackground.html
@@ -69,7 +69,7 @@
}
});
ImageBackground
A common feature request from developers familiar with the web is background-image. To handle this use case, you can use the <ImageBackground> component, which has the same props as <Image>, and add whatever children to it you would like to layer on top of it.
You might not want to use <ImageBackground> in some cases, since the implementation is very simple. Refer to <ImageBackground>'s source code for more insight, and create your own custom component when needed.
You might not want to use <ImageBackground> in some cases, since the implementation is very basic. Refer to <ImageBackground>'s source code for more insight, and create your own custom component when needed.
Note that you must specify some width and height style attributes.
Example
return (
diff --git a/docs/0.55/imagebackground/index.html b/docs/0.55/imagebackground/index.html
index f25d6909fa3..d08dbe3c3a6 100644
--- a/docs/0.55/imagebackground/index.html
+++ b/docs/0.55/imagebackground/index.html
@@ -69,7 +69,7 @@
}
});
ImageBackground
A common feature request from developers familiar with the web is background-image. To handle this use case, you can use the <ImageBackground> component, which has the same props as <Image>, and add whatever children to it you would like to layer on top of it.
You might not want to use <ImageBackground> in some cases, since the implementation is very simple. Refer to <ImageBackground>'s source code for more insight, and create your own custom component when needed.
You might not want to use <ImageBackground> in some cases, since the implementation is very basic. Refer to <ImageBackground>'s source code for more insight, and create your own custom component when needed.
Note that you must specify some width and height style attributes.
Example
return (
diff --git a/docs/0.56/imagebackground.html b/docs/0.56/imagebackground.html
index 58d4a0c5f66..cec05ad0238 100644
--- a/docs/0.56/imagebackground.html
+++ b/docs/0.56/imagebackground.html
@@ -69,7 +69,7 @@
}
});
ImageBackground
A common feature request from developers familiar with the web is background-image. To handle this use case, you can use the <ImageBackground> component, which has the same props as <Image>, and add whatever children to it you would like to layer on top of it.
You might not want to use <ImageBackground> in some cases, since the implementation is very simple. Refer to <ImageBackground>'s source code for more insight, and create your own custom component when needed.
You might not want to use <ImageBackground> in some cases, since the implementation is very basic. Refer to <ImageBackground>'s source code for more insight, and create your own custom component when needed.
Note that you must specify some width and height style attributes.
Example
return (
diff --git a/docs/0.56/imagebackground/index.html b/docs/0.56/imagebackground/index.html
index 58d4a0c5f66..cec05ad0238 100644
--- a/docs/0.56/imagebackground/index.html
+++ b/docs/0.56/imagebackground/index.html
@@ -69,7 +69,7 @@
}
});
ImageBackground
A common feature request from developers familiar with the web is background-image. To handle this use case, you can use the <ImageBackground> component, which has the same props as <Image>, and add whatever children to it you would like to layer on top of it.
You might not want to use <ImageBackground> in some cases, since the implementation is very simple. Refer to <ImageBackground>'s source code for more insight, and create your own custom component when needed.
You might not want to use <ImageBackground> in some cases, since the implementation is very basic. Refer to <ImageBackground>'s source code for more insight, and create your own custom component when needed.
Note that you must specify some width and height style attributes.
Example
return (
diff --git a/docs/0.57/imagebackground.html b/docs/0.57/imagebackground.html
index 6b98d5ef8f0..65d350adb1c 100644
--- a/docs/0.57/imagebackground.html
+++ b/docs/0.57/imagebackground.html
@@ -69,7 +69,7 @@
}
});
ImageBackground
A common feature request from developers familiar with the web is background-image. To handle this use case, you can use the <ImageBackground> component, which has the same props as <Image>, and add whatever children to it you would like to layer on top of it.
You might not want to use <ImageBackground> in some cases, since the implementation is very simple. Refer to <ImageBackground>'s source code for more insight, and create your own custom component when needed.
You might not want to use <ImageBackground> in some cases, since the implementation is very basic. Refer to <ImageBackground>'s source code for more insight, and create your own custom component when needed.
Note that you must specify some width and height style attributes.
Example
return (
diff --git a/docs/0.57/imagebackground/index.html b/docs/0.57/imagebackground/index.html
index 6b98d5ef8f0..65d350adb1c 100644
--- a/docs/0.57/imagebackground/index.html
+++ b/docs/0.57/imagebackground/index.html
@@ -69,7 +69,7 @@
}
});
ImageBackground
A common feature request from developers familiar with the web is background-image. To handle this use case, you can use the <ImageBackground> component, which has the same props as <Image>, and add whatever children to it you would like to layer on top of it.
You might not want to use <ImageBackground> in some cases, since the implementation is very simple. Refer to <ImageBackground>'s source code for more insight, and create your own custom component when needed.
You might not want to use <ImageBackground> in some cases, since the implementation is very basic. Refer to <ImageBackground>'s source code for more insight, and create your own custom component when needed.
Note that you must specify some width and height style attributes.
Example
return (