Skip to content
This repository has been archived by the owner on Jun 21, 2018. It is now read-only.

Latest commit

 

History

History
31 lines (22 loc) · 1.23 KB

known-issues.md

File metadata and controls

31 lines (22 loc) · 1.23 KB
Raw

Known issues

Safari flexbox performance

Safari version prior to 10.1 can suffer from extremely poor flexbox performance. The recommended way to work around this issue (as used on mobile.twitter.com) is to set display:block on Views in your element hierarchy that you know don't need flexbox layout.

Missing modules and components

Not all of the views present on iOS/Android are currently available on Web. We are very much interested in the community's feedback on the next set of modules and views.

Not all the modules or views for iOS/Android can be implemented on Web. In some cases it will be necessary to use a Web counterpart or to guard the use of a module with Platform.OS (e.g. NativeModules)

Missing component props

There are properties that do not work across all platforms. All web-specific props are annotated with (web) in the documentation.

Platform parity

There are some known issues in React Native where APIs could be made more consistent between platforms. For example, React Native for Web includes ActivityIndicator and a horizontal ProgressBar for Web use, in anticipation of the convergence between the iOS and Android components in React Native.