Update KnownIssues.md
This commit is contained in:
parent
0bf7928ebe
commit
5950f8cf15
|
@ -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:
|
||||
|
||||
- `<AndroidViewPager>` (to be open sourced soon) and `<ScrollView pagingEnabled={true}>` on iOS do a similar thing. We might want to unify them to `<ViewPager>`.
|
||||
- `<AndroidViewPager>` and `<ScrollView pagingEnabled={true}>` on iOS do a similar thing. We might want to unify them to `<ViewPager>`.
|
||||
- `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
|
||||
|
||||
|
|
Loading…
Reference in New Issue