From 5950f8cf1564905daa88d1b5e0aacd8e96fbaf71 Mon Sep 17 00:00:00 2001 From: Martin Konicek Date: Thu, 19 Nov 2015 18:10:40 +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 6ce63307e..9fc543299 100644 --- a/docs/KnownIssues.md +++ b/docs/KnownIssues.md @@ -53,11 +53,11 @@ There are properties that work on one platform only, either because they can inh There are known cases where the APIs could be made more consistent across iOS and Android: -- `` (to be open sourced soon) and `` on iOS do a similar thing. We might want to unify them to ``. +- `` and `` on iOS do a similar thing. We might want to unify them to ``. - `alert()` needs Android support (once the Dialogs module is open sourced) - It might be possible to bring `LinkingIOS` and `IntentAndroid` (to be open sourced) closer together. - `ActivityIndicator` could render a native spinning indicator on both platforms (currently this is done using `ActivityIndicatorIOS` on iOS and `ProgressBarAndroid` on Android). -- `ProgressBar` could render a horizontal progress bar on both platforms (currently only supported on iOS via `ProgressViewIOS`). +- `ProgressBar` could render a horizontal progress bar on both platforms (on iOS this is `ProgressViewIOS`, on Android it's `ProgressBarAndroid`). ### Publishing modules on Android