From 0f89696f76845925de425bbd6dd29cae8e5f0b43 Mon Sep 17 00:00:00 2001 From: Martin Konicek Date: Thu, 26 Nov 2015 17:39:15 +0000 Subject: [PATCH] Update KnownIssues.md --- docs/KnownIssues.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/KnownIssues.md b/docs/KnownIssues.md index 0af787604..b7a219d59 100644 --- a/docs/KnownIssues.md +++ b/docs/KnownIssues.md @@ -69,9 +69,9 @@ This is a result of how Android rendering works. This feature is not being worke Another issue with `overflow: 'hidden'` on Android: a view is not clipped by the parent's `borderRadius` even if the parent has `overflow: 'hidden'` enabled – the corners of the inner view will be visible outside of the rounded corners. This is only on Android; it works as expected on iOS. See a [demo of the bug](https://rnplay.org/apps/BlGjdQ) and the [corresponding issue](https://github.com/facebook/react-native/issues/3198). -### No support for shadows on Android +### View shadows -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](https://developer.android.com/training/material/shadows-clipping.html), but more experimentation will be required. +The `shadow*` [view styles](/react-native/docs/view.html#style) apply on iOS, and the `elevation` view prop is available on Android. Setting `elevation` on Android is equivalent to using the [native elevation API](https://developer.android.com/training/material/shadows-clipping.html#Elevation), and has the same limitations (most significantly, it only works on Android 5.0+). Setting `elevation` on Android also affects the z-order for overlapping views. ### Android M permissions