From b3d7332dddbfe57b1e4448c2d7991d364010f118 Mon Sep 17 00:00:00 2001 From: Nicolas Gallagher Date: Tue, 8 Mar 2016 09:33:56 -0800 Subject: [PATCH] Update 'known issues' guide --- docs/guides/known-issues.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/guides/known-issues.md b/docs/guides/known-issues.md index 7c223315..510e6d1b 100644 --- a/docs/guides/known-issues.md +++ b/docs/guides/known-issues.md @@ -7,7 +7,8 @@ views present on iOS/Android are released 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. +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 @@ -18,4 +19,5 @@ props are annotated with `(web)` in the documentation. 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`. +`ActivityIndicator` and a horizontal `ProgressBar` for Web use, in anticipation +of the convergence between the iOS and Android components in React Native.