From 8752e2b03599174342687a70a7cd4e018caab763 Mon Sep 17 00:00:00 2001 From: Travis CI Date: Sat, 14 Nov 2015 19:38:27 +0000 Subject: [PATCH] update website --- docs/known-issues.html | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/known-issues.html b/docs/known-issues.html index d85e75df5b2..50bb2ef722a 100644 --- a/docs/known-issues.html +++ b/docs/known-issues.html @@ -14,8 +14,7 @@ Pasteboard PushNotificationIOS Alert

Some props are only supported on one platform #

There are properties that work on one platform only, either because they can inherently only be supported on that platform or because they haven't been implemented on the other platforms yet. All of these are annotated with @platform in JS docs and have a small badge next to them on the website. See e.g. Image.

Platform parity #

There are known cases where the APIs could be made more consistent across iOS and Android:

Publishing modules on Android #

There is currently no easy way of publishing custom native modules on Android. Smooth work flow for contributors is important and this will be looked at very closely after the initial Open Source release. Of course the aim will be to streamline and optimize the process between iOS and Android as much as possible.

The 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.

No support for shadows on Android #

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.

Layout-only nodes on Android #

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:

<View collapsable={false}> ... -</View>

Memory issues with PNG images #

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.

react-native init hangs #

Try running react-native init with --verbose and see #2797 for common causes.

Text Input Border #

The text input has by default a border at the bottom of its view. This border has its padding set by the background image provided by the system, and it cannot be changed. Solutions to avoid this is to either not set height explicitly, case in which the system will take care of displaying the border in the correct position, or to not display the border by setting underlineColor to transparent.

Firebase throws 'No transports available' #

Make sure you require React Native before requiring Firebase. This way React Native has a chance to set up the WebSocket polyfill:

var React = require('react-native') -var Firebase = require('firebase');

Discovered thanks to issue #3645. If you're curious, the polyfills are set up in InitializeJavaScriptAppEngine.js.

Next →