2015-01-30 01:10:49 +00:00
|
|
|
/**
|
2017-05-06 03:50:47 +00:00
|
|
|
* Copyright (c) 2015-present, Facebook, Inc.
|
Implement CSS z-index for iOS
Summary:
This diff implement the CSS z-index for React Native iOS views. We've had numerous pull request for this feature, but they've all attempted to use the `layer.zPosition` property, which is problematic for two reasons:
1. zPosition only affects rendering order, not event processing order. Views with a higher zPosition will appear in front of others in the hierarchy, but won't be the first to receive touch events, and may be blocked by views that are visually behind them.
2. when using a perspective transform matrix, views with a nonzero zPosition will be rendered in a different position due to parallax, which probably isn't desirable.
See https://github.com/facebook/react-native/pull/7825 for further discussion of this problem.
So instead of using `layer.zPosition`, I've implemented this by actually adjusting the order of the subviews within their parent based on the zIndex. This can't be done on the JS side because it would affect layout, which is order-dependent, so I'm doing it inside the view itself.
It works as follows:
1. The `reactSubviews` array is set, whose order matches the order of the JS components and shadowView components, as specified by the UIManager.
2. `didUpdateReactSubviews` is called, which in turn calls `sortedSubviews` (which lazily generates a sorted array of `reactSubviews` by zIndex) and inserts the result into the view.
3. If a subview is added or removed, or the zIndex of any subview is changed, the previous `sortedSubviews` array is cleared and `didUpdateReactSubviews` is called again.
To demonstrate it working, I've modified the UIExplorer example from https://github.com/facebook/react-native/pull/7825
Reviewed By: javache
Differential Revision: D3365717
fbshipit-source-id: b34aa8bfad577bce023f8af5414f9b974aafd8aa
2016-06-07 14:40:25 +00:00
|
|
|
* All rights reserved.
|
|
|
|
*
|
|
|
|
* This source code is licensed under the BSD-style license found in the
|
|
|
|
* LICENSE file in the root directory of this source tree. An additional grant
|
|
|
|
* of patent rights can be found in the PATENTS file in the same directory.
|
|
|
|
*
|
2015-03-23 22:07:33 +00:00
|
|
|
* @flow
|
2017-02-25 11:05:32 +00:00
|
|
|
* @providesModule ViewExample
|
2015-01-30 01:10:49 +00:00
|
|
|
*/
|
|
|
|
'use strict';
|
|
|
|
|
2016-04-09 03:36:40 +00:00
|
|
|
var React = require('react');
|
|
|
|
var ReactNative = require('react-native');
|
2015-01-30 01:10:49 +00:00
|
|
|
var {
|
|
|
|
StyleSheet,
|
|
|
|
Text,
|
|
|
|
View,
|
2016-04-09 03:36:40 +00:00
|
|
|
} = ReactNative;
|
2015-07-03 02:16:29 +00:00
|
|
|
var TouchableWithoutFeedback = require('TouchableWithoutFeedback');
|
2015-01-30 01:10:49 +00:00
|
|
|
|
2015-03-25 03:33:17 +00:00
|
|
|
var styles = StyleSheet.create({
|
|
|
|
box: {
|
|
|
|
backgroundColor: '#527FE4',
|
|
|
|
borderColor: '#000033',
|
|
|
|
borderWidth: 1,
|
Implement CSS z-index for iOS
Summary:
This diff implement the CSS z-index for React Native iOS views. We've had numerous pull request for this feature, but they've all attempted to use the `layer.zPosition` property, which is problematic for two reasons:
1. zPosition only affects rendering order, not event processing order. Views with a higher zPosition will appear in front of others in the hierarchy, but won't be the first to receive touch events, and may be blocked by views that are visually behind them.
2. when using a perspective transform matrix, views with a nonzero zPosition will be rendered in a different position due to parallax, which probably isn't desirable.
See https://github.com/facebook/react-native/pull/7825 for further discussion of this problem.
So instead of using `layer.zPosition`, I've implemented this by actually adjusting the order of the subviews within their parent based on the zIndex. This can't be done on the JS side because it would affect layout, which is order-dependent, so I'm doing it inside the view itself.
It works as follows:
1. The `reactSubviews` array is set, whose order matches the order of the JS components and shadowView components, as specified by the UIManager.
2. `didUpdateReactSubviews` is called, which in turn calls `sortedSubviews` (which lazily generates a sorted array of `reactSubviews` by zIndex) and inserts the result into the view.
3. If a subview is added or removed, or the zIndex of any subview is changed, the previous `sortedSubviews` array is cleared and `didUpdateReactSubviews` is called again.
To demonstrate it working, I've modified the UIExplorer example from https://github.com/facebook/react-native/pull/7825
Reviewed By: javache
Differential Revision: D3365717
fbshipit-source-id: b34aa8bfad577bce023f8af5414f9b974aafd8aa
2016-06-07 14:40:25 +00:00
|
|
|
},
|
|
|
|
zIndex: {
|
|
|
|
justifyContent: 'space-around',
|
|
|
|
width: 100,
|
|
|
|
height: 50,
|
|
|
|
marginTop: -10,
|
|
|
|
},
|
2015-03-25 03:33:17 +00:00
|
|
|
});
|
2015-01-30 01:10:49 +00:00
|
|
|
|
2017-08-18 01:36:54 +00:00
|
|
|
class ViewBorderStyleExample extends React.Component<{}, $FlowFixMeState> {
|
2016-07-26 08:00:02 +00:00
|
|
|
state = {
|
|
|
|
showBorder: true
|
|
|
|
};
|
2015-07-03 02:16:29 +00:00
|
|
|
|
|
|
|
render() {
|
|
|
|
return (
|
|
|
|
<TouchableWithoutFeedback onPress={this._handlePress}>
|
|
|
|
<View>
|
|
|
|
<View style={{
|
|
|
|
borderWidth: 1,
|
|
|
|
borderStyle: this.state.showBorder ? 'dashed' : null,
|
|
|
|
padding: 5
|
|
|
|
}}>
|
|
|
|
<Text style={{fontSize: 11}}>
|
|
|
|
Dashed border style
|
|
|
|
</Text>
|
|
|
|
</View>
|
|
|
|
<View style={{
|
|
|
|
marginTop: 5,
|
|
|
|
borderWidth: 1,
|
|
|
|
borderRadius: 5,
|
|
|
|
borderStyle: this.state.showBorder ? 'dotted' : null,
|
|
|
|
padding: 5
|
|
|
|
}}>
|
|
|
|
<Text style={{fontSize: 11}}>
|
|
|
|
Dotted border style
|
|
|
|
</Text>
|
|
|
|
</View>
|
|
|
|
</View>
|
|
|
|
</TouchableWithoutFeedback>
|
|
|
|
);
|
2016-07-26 08:00:02 +00:00
|
|
|
}
|
2015-07-03 02:16:29 +00:00
|
|
|
|
2016-07-26 08:00:02 +00:00
|
|
|
_handlePress = () => {
|
2015-07-03 02:16:29 +00:00
|
|
|
this.setState({showBorder: !this.state.showBorder});
|
2016-07-26 08:00:02 +00:00
|
|
|
};
|
|
|
|
}
|
2015-07-03 02:16:29 +00:00
|
|
|
|
2017-08-18 01:36:54 +00:00
|
|
|
class ZIndexExample extends React.Component<{}, $FlowFixMeState> {
|
2016-07-26 08:00:02 +00:00
|
|
|
state = {
|
|
|
|
flipped: false
|
|
|
|
};
|
2016-06-29 14:38:30 +00:00
|
|
|
|
Implement CSS z-index for iOS
Summary:
This diff implement the CSS z-index for React Native iOS views. We've had numerous pull request for this feature, but they've all attempted to use the `layer.zPosition` property, which is problematic for two reasons:
1. zPosition only affects rendering order, not event processing order. Views with a higher zPosition will appear in front of others in the hierarchy, but won't be the first to receive touch events, and may be blocked by views that are visually behind them.
2. when using a perspective transform matrix, views with a nonzero zPosition will be rendered in a different position due to parallax, which probably isn't desirable.
See https://github.com/facebook/react-native/pull/7825 for further discussion of this problem.
So instead of using `layer.zPosition`, I've implemented this by actually adjusting the order of the subviews within their parent based on the zIndex. This can't be done on the JS side because it would affect layout, which is order-dependent, so I'm doing it inside the view itself.
It works as follows:
1. The `reactSubviews` array is set, whose order matches the order of the JS components and shadowView components, as specified by the UIManager.
2. `didUpdateReactSubviews` is called, which in turn calls `sortedSubviews` (which lazily generates a sorted array of `reactSubviews` by zIndex) and inserts the result into the view.
3. If a subview is added or removed, or the zIndex of any subview is changed, the previous `sortedSubviews` array is cleared and `didUpdateReactSubviews` is called again.
To demonstrate it working, I've modified the UIExplorer example from https://github.com/facebook/react-native/pull/7825
Reviewed By: javache
Differential Revision: D3365717
fbshipit-source-id: b34aa8bfad577bce023f8af5414f9b974aafd8aa
2016-06-07 14:40:25 +00:00
|
|
|
render() {
|
|
|
|
const indices = this.state.flipped ? [-1, 0, 1, 2] : [2, 1, 0, -1];
|
|
|
|
return (
|
|
|
|
<TouchableWithoutFeedback onPress={this._handlePress}>
|
|
|
|
<View>
|
|
|
|
<Text style={{paddingBottom: 10}}>Tap to flip sorting order</Text>
|
|
|
|
<View style={[
|
|
|
|
styles.zIndex,
|
|
|
|
{marginTop: 0, backgroundColor: '#E57373', zIndex: indices[0]}
|
|
|
|
]}>
|
|
|
|
<Text>ZIndex {indices[0]}</Text>
|
|
|
|
</View>
|
|
|
|
<View style={[
|
|
|
|
styles.zIndex,
|
|
|
|
{marginLeft: 50, backgroundColor: '#FFF176', zIndex: indices[1]}
|
|
|
|
]}>
|
|
|
|
<Text>ZIndex {indices[1]}</Text>
|
|
|
|
</View>
|
|
|
|
<View style={[
|
|
|
|
styles.zIndex,
|
|
|
|
{marginLeft: 100, backgroundColor: '#81C784', zIndex: indices[2]}
|
|
|
|
]}>
|
|
|
|
<Text>ZIndex {indices[2]}</Text>
|
|
|
|
</View>
|
|
|
|
<View style={[
|
|
|
|
styles.zIndex,
|
|
|
|
{marginLeft: 150, backgroundColor: '#64B5F6', zIndex: indices[3]}
|
|
|
|
]}>
|
|
|
|
<Text>ZIndex {indices[3]}</Text>
|
|
|
|
</View>
|
|
|
|
</View>
|
|
|
|
</TouchableWithoutFeedback>
|
|
|
|
);
|
2016-07-26 08:00:02 +00:00
|
|
|
}
|
2016-06-29 14:38:30 +00:00
|
|
|
|
2016-07-26 08:00:02 +00:00
|
|
|
_handlePress = () => {
|
Implement CSS z-index for iOS
Summary:
This diff implement the CSS z-index for React Native iOS views. We've had numerous pull request for this feature, but they've all attempted to use the `layer.zPosition` property, which is problematic for two reasons:
1. zPosition only affects rendering order, not event processing order. Views with a higher zPosition will appear in front of others in the hierarchy, but won't be the first to receive touch events, and may be blocked by views that are visually behind them.
2. when using a perspective transform matrix, views with a nonzero zPosition will be rendered in a different position due to parallax, which probably isn't desirable.
See https://github.com/facebook/react-native/pull/7825 for further discussion of this problem.
So instead of using `layer.zPosition`, I've implemented this by actually adjusting the order of the subviews within their parent based on the zIndex. This can't be done on the JS side because it would affect layout, which is order-dependent, so I'm doing it inside the view itself.
It works as follows:
1. The `reactSubviews` array is set, whose order matches the order of the JS components and shadowView components, as specified by the UIManager.
2. `didUpdateReactSubviews` is called, which in turn calls `sortedSubviews` (which lazily generates a sorted array of `reactSubviews` by zIndex) and inserts the result into the view.
3. If a subview is added or removed, or the zIndex of any subview is changed, the previous `sortedSubviews` array is cleared and `didUpdateReactSubviews` is called again.
To demonstrate it working, I've modified the UIExplorer example from https://github.com/facebook/react-native/pull/7825
Reviewed By: javache
Differential Revision: D3365717
fbshipit-source-id: b34aa8bfad577bce023f8af5414f9b974aafd8aa
2016-06-07 14:40:25 +00:00
|
|
|
this.setState({flipped: !this.state.flipped});
|
2016-07-26 08:00:02 +00:00
|
|
|
};
|
|
|
|
}
|
Implement CSS z-index for iOS
Summary:
This diff implement the CSS z-index for React Native iOS views. We've had numerous pull request for this feature, but they've all attempted to use the `layer.zPosition` property, which is problematic for two reasons:
1. zPosition only affects rendering order, not event processing order. Views with a higher zPosition will appear in front of others in the hierarchy, but won't be the first to receive touch events, and may be blocked by views that are visually behind them.
2. when using a perspective transform matrix, views with a nonzero zPosition will be rendered in a different position due to parallax, which probably isn't desirable.
See https://github.com/facebook/react-native/pull/7825 for further discussion of this problem.
So instead of using `layer.zPosition`, I've implemented this by actually adjusting the order of the subviews within their parent based on the zIndex. This can't be done on the JS side because it would affect layout, which is order-dependent, so I'm doing it inside the view itself.
It works as follows:
1. The `reactSubviews` array is set, whose order matches the order of the JS components and shadowView components, as specified by the UIManager.
2. `didUpdateReactSubviews` is called, which in turn calls `sortedSubviews` (which lazily generates a sorted array of `reactSubviews` by zIndex) and inserts the result into the view.
3. If a subview is added or removed, or the zIndex of any subview is changed, the previous `sortedSubviews` array is cleared and `didUpdateReactSubviews` is called again.
To demonstrate it working, I've modified the UIExplorer example from https://github.com/facebook/react-native/pull/7825
Reviewed By: javache
Differential Revision: D3365717
fbshipit-source-id: b34aa8bfad577bce023f8af5414f9b974aafd8aa
2016-06-07 14:40:25 +00:00
|
|
|
|
2015-03-25 03:33:17 +00:00
|
|
|
exports.title = '<View>';
|
2015-09-15 21:46:54 +00:00
|
|
|
exports.description = 'Basic building block of all UI, examples that ' +
|
|
|
|
'demonstrate some of the many styles available.';
|
|
|
|
|
2015-03-25 03:33:17 +00:00
|
|
|
exports.displayName = 'ViewExample';
|
|
|
|
exports.examples = [
|
|
|
|
{
|
|
|
|
title: 'Background Color',
|
|
|
|
render: function() {
|
|
|
|
return (
|
|
|
|
<View style={{backgroundColor: '#527FE4', padding: 5}}>
|
|
|
|
<Text style={{fontSize: 11}}>
|
|
|
|
Blue background
|
|
|
|
</Text>
|
|
|
|
</View>
|
|
|
|
);
|
|
|
|
},
|
|
|
|
}, {
|
|
|
|
title: 'Border',
|
|
|
|
render: function() {
|
|
|
|
return (
|
|
|
|
<View style={{borderColor: '#527FE4', borderWidth: 5, padding: 10}}>
|
|
|
|
<Text style={{fontSize: 11}}>5px blue border</Text>
|
|
|
|
</View>
|
|
|
|
);
|
|
|
|
},
|
|
|
|
}, {
|
|
|
|
title: 'Padding/Margin',
|
|
|
|
render: function() {
|
|
|
|
return (
|
|
|
|
<View style={{borderColor: '#bb0000', borderWidth: 0.5}}>
|
|
|
|
<View style={[styles.box, {padding: 5}]}>
|
|
|
|
<Text style={{fontSize: 11}}>5px padding</Text>
|
2015-01-30 01:10:49 +00:00
|
|
|
</View>
|
2015-03-25 03:33:17 +00:00
|
|
|
<View style={[styles.box, {margin: 5}]}>
|
|
|
|
<Text style={{fontSize: 11}}>5px margin</Text>
|
2015-01-30 01:10:49 +00:00
|
|
|
</View>
|
2015-03-25 03:33:17 +00:00
|
|
|
<View style={[styles.box, {margin: 5, padding: 5, alignSelf: 'flex-start'}]}>
|
2015-01-30 01:10:49 +00:00
|
|
|
<Text style={{fontSize: 11}}>
|
2015-03-25 03:33:17 +00:00
|
|
|
5px margin and padding,
|
|
|
|
</Text>
|
|
|
|
<Text style={{fontSize: 11}}>
|
|
|
|
widthAutonomous=true
|
2015-01-30 01:10:49 +00:00
|
|
|
</Text>
|
|
|
|
</View>
|
2015-03-25 03:33:17 +00:00
|
|
|
</View>
|
|
|
|
);
|
|
|
|
},
|
|
|
|
}, {
|
|
|
|
title: 'Border Radius',
|
|
|
|
render: function() {
|
|
|
|
return (
|
|
|
|
<View style={{borderWidth: 0.5, borderRadius: 5, padding: 5}}>
|
|
|
|
<Text style={{fontSize: 11}}>
|
|
|
|
Too much use of `borderRadius` (especially large radii) on
|
|
|
|
anything which is scrolling may result in dropped frames.
|
|
|
|
Use sparingly.
|
|
|
|
</Text>
|
|
|
|
</View>
|
|
|
|
);
|
|
|
|
},
|
2015-07-03 02:16:29 +00:00
|
|
|
}, {
|
|
|
|
title: 'Border Style',
|
|
|
|
render: function() {
|
|
|
|
return <ViewBorderStyleExample />;
|
|
|
|
},
|
2015-03-25 03:33:17 +00:00
|
|
|
}, {
|
|
|
|
title: 'Circle with Border Radius',
|
|
|
|
render: function() {
|
|
|
|
return (
|
|
|
|
<View style={{borderRadius: 10, borderWidth: 1, width: 20, height: 20}} />
|
|
|
|
);
|
|
|
|
},
|
|
|
|
}, {
|
|
|
|
title: 'Overflow',
|
|
|
|
render: function() {
|
|
|
|
return (
|
|
|
|
<View style={{flexDirection: 'row'}}>
|
|
|
|
<View
|
|
|
|
style={{
|
|
|
|
width: 95,
|
|
|
|
height: 10,
|
|
|
|
marginRight: 10,
|
|
|
|
marginBottom: 5,
|
|
|
|
overflow: 'hidden',
|
|
|
|
borderWidth: 0.5,
|
|
|
|
}}>
|
|
|
|
<View style={{width: 200, height: 20}}>
|
|
|
|
<Text>Overflow hidden</Text>
|
2015-01-30 01:10:49 +00:00
|
|
|
</View>
|
2015-03-25 03:33:17 +00:00
|
|
|
</View>
|
|
|
|
<View style={{width: 95, height: 10, marginBottom: 5, borderWidth: 0.5}}>
|
|
|
|
<View style={{width: 200, height: 20}}>
|
|
|
|
<Text>Overflow visible</Text>
|
2015-01-30 01:10:49 +00:00
|
|
|
</View>
|
|
|
|
</View>
|
2015-03-25 03:33:17 +00:00
|
|
|
</View>
|
|
|
|
);
|
|
|
|
},
|
|
|
|
}, {
|
|
|
|
title: 'Opacity',
|
|
|
|
render: function() {
|
|
|
|
return (
|
|
|
|
<View>
|
2015-01-30 01:10:49 +00:00
|
|
|
<View style={{opacity: 0}}><Text>Opacity 0</Text></View>
|
|
|
|
<View style={{opacity: 0.1}}><Text>Opacity 0.1</Text></View>
|
|
|
|
<View style={{opacity: 0.3}}><Text>Opacity 0.3</Text></View>
|
|
|
|
<View style={{opacity: 0.5}}><Text>Opacity 0.5</Text></View>
|
|
|
|
<View style={{opacity: 0.7}}><Text>Opacity 0.7</Text></View>
|
|
|
|
<View style={{opacity: 0.9}}><Text>Opacity 0.9</Text></View>
|
|
|
|
<View style={{opacity: 1}}><Text>Opacity 1</Text></View>
|
2015-03-25 03:33:17 +00:00
|
|
|
</View>
|
|
|
|
);
|
|
|
|
},
|
Implement CSS z-index for iOS
Summary:
This diff implement the CSS z-index for React Native iOS views. We've had numerous pull request for this feature, but they've all attempted to use the `layer.zPosition` property, which is problematic for two reasons:
1. zPosition only affects rendering order, not event processing order. Views with a higher zPosition will appear in front of others in the hierarchy, but won't be the first to receive touch events, and may be blocked by views that are visually behind them.
2. when using a perspective transform matrix, views with a nonzero zPosition will be rendered in a different position due to parallax, which probably isn't desirable.
See https://github.com/facebook/react-native/pull/7825 for further discussion of this problem.
So instead of using `layer.zPosition`, I've implemented this by actually adjusting the order of the subviews within their parent based on the zIndex. This can't be done on the JS side because it would affect layout, which is order-dependent, so I'm doing it inside the view itself.
It works as follows:
1. The `reactSubviews` array is set, whose order matches the order of the JS components and shadowView components, as specified by the UIManager.
2. `didUpdateReactSubviews` is called, which in turn calls `sortedSubviews` (which lazily generates a sorted array of `reactSubviews` by zIndex) and inserts the result into the view.
3. If a subview is added or removed, or the zIndex of any subview is changed, the previous `sortedSubviews` array is cleared and `didUpdateReactSubviews` is called again.
To demonstrate it working, I've modified the UIExplorer example from https://github.com/facebook/react-native/pull/7825
Reviewed By: javache
Differential Revision: D3365717
fbshipit-source-id: b34aa8bfad577bce023f8af5414f9b974aafd8aa
2016-06-07 14:40:25 +00:00
|
|
|
}, {
|
|
|
|
title: 'ZIndex',
|
|
|
|
render: function() {
|
|
|
|
return <ZIndexExample />;
|
|
|
|
},
|
2015-01-30 01:10:49 +00:00
|
|
|
},
|
2015-03-25 03:33:17 +00:00
|
|
|
];
|