marhaupe
1169ed0946
fix: android textinput gets blurred after navigating back
...
When navigating from ScreenA to ScreenB and then back to ScreenA,
react-navigation unconditionally calls `Keyboard.dismiss()`.
If the user is fast enough and taps on a `TextInput` after coming
back from ScreenB, the keyboard opens, just to be dismissed again.
This would also happen if some logic automatically focuses the
`TextInput` in ScreenA. This behaviour can be seen observed in
https://snack.expo.io/lTDZhVNhV .
2020-11-04 22:35:57 +01:00
Satyajit Sahoo
2bb6603aa3
chore: upgrade depenendecies
2020-09-23 01:34:55 +02:00
Satyajit Sahoo
f00091d7ab
refactor: use ts-expect-errpr instead of ts-ignore
2020-06-24 20:07:32 +02:00
Kang Byung Seon
35d6b9e3a4
fix: don't use deprecated currentlyFocusedField ( #8365 )
...
Co-authored-by: Satyajit Sahoo <satyajit.happy@gmail.com >
2020-06-15 15:12:56 +02:00
max
8432e5ab25
fix: dismiss keyboard on screen change for android
2020-03-30 21:50:52 +02:00
Satyajit Sahoo
b1fe73097f
fix: only dismiss previously focused input on page change. closes #6918
2020-03-19 18:30:54 +01:00
Satyajit Sahoo
87d28ca430
refactor: minor tweaks
2020-01-03 17:07:42 +01:00
Satyajit Sahoo
c52a8c46a8
fix: fix typescript issues
2019-12-19 14:39:35 +01:00
osdnk
876c3183e1
fix: make clearKeyboardTimeout private
2019-10-25 09:29:36 +02:00
osdnk
07bfc86327
fix: keyboard manager in stack for fast swipe
2019-10-24 18:50:16 +02:00
satyajit.happy
f0b80ce0f6
feat: implement various navigators
2019-08-19 01:07:48 +05:30
satyajit.happy
267d7c214f
refactor: don't use keyboardAwareNavigator The HOC currently forces us to expose some options in stack config which we don't want to. So we vendor this functionality for now to avoid this.
2019-08-18 23:51:48 +05:30
