The behavior on Android is what you would expect from the web as well. If you want to be able to click through an overlaying transparent view, you can set pointerEvents='none' on it.
overflow style property defaults to hidden and cannot be changed on Android #This is a result of how Android rendering works. This feature is not being worked on as it would be a significant undertaking and there are many more important tasks.
We don't support shadows on Android currently. These are notoriously hard to implement as they require drawing outside of a view's bounds and Android's invalidation logic has a hard time with that. A possible solution is to use elevation, but more experimentation will be required.
An optimization feature of the Android version of React Native is for views which only contribute to the layout to not have a native view, only their layout properties are propagated to their children views. This optimization is to provide stability in deep view hierarchies for React Native and gis therefore enabled by default. Should you depend on a view being present or internal tests incorrectly detect a view is layout only it will be necessary to turn off this behavior. To do this, set collapsable to false as in this example:
The behavior on Android is what you would expect from the web as well. If you want to be able to click through an overlaying transparent view, you can set pointerEvents='none' on it.
overflow style property defaults to hidden and cannot be changed on Android #This is a result of how Android rendering works. This feature is not being worked on as it would be a significant undertaking and there are many more important tasks.
We don't support shadows on Android currently. These are notoriously hard to implement as they require drawing outside of a view's bounds and Android's invalidation logic has a hard time with that. A possible solution is to use elevation, but more experimentation will be required.
An optimization feature of the Android version of React Native is for views which only contribute to the layout to not have a native view, only their layout properties are propagated to their children views. This optimization is to provide stability in deep view hierarchies for React Native and is therefore enabled by default. Should you depend on a view being present or internal tests incorrectly detect a view is layout only it will be necessary to turn off this behavior. To do this, set collapsable to false as in this example:
React Native Android depends on Fresco for loading and displaying images. Currently we have disabled downsampling because it is experimental, so you may run into memory issues when loading large PNG images.