You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Basically, when some View is under KeyboardAwareScrollView, the KeyboardAwareScrollView scroll Input up exactly like the height of View here is a video example
Screen.Recording.2023-03-17.at.19.04.21.mov
Pseudocode example:
<><KeyboardAwareScrollViewContainer// https://github.com/APSL/react-native-keyboard-aware-scroll-view/issues/418#issuecomment-617474009keyboardOpeningTime={Number.MAX_SAFE_INTEGER}><View><Text>Hello</Text><Input/>{/*... a lot of inputs */}</View></KeyboardAwareScrollViewContainer><Viewstyle={{height: 100}}/></>
Expected behavior: KeyboardAwareScrollView scroll Input without extra scrolling Input up
Current workaround: use onLayout on View under KeyboardAwareScrollView
const[extraScrollHeight,setExtraScrollHeight]=useState(0)...<><KeyboardAwareScrollViewContainerextraScrollHeight={-extraScrollHeight}// https://github.com/APSL/react-native-keyboard-aware-scroll-view/issues/418#issuecomment-617474009keyboardOpeningTime={Number.MAX_SAFE_INTEGER}><View><Text>Hello</Text><Input/>{/*... a lot of inputs */}</View></KeyboardAwareScrollViewContainer><ViewonLayout={e=>setExtraScrollHeight(e.nativeEvent.layout.height)}style={{height: 100}}/></>
WITH WORKAROUND:
Screen.Recording.2023-03-17.at.19.13.03.mov
UPD: I believe this PR should fix this issue - #426
The text was updated successfully, but these errors were encountered:
Issue:
Basically, when some View is under KeyboardAwareScrollView, the KeyboardAwareScrollView scroll Input up exactly like the height of View here is a video example
Screen.Recording.2023-03-17.at.19.04.21.mov
Pseudocode example:
Expected behavior: KeyboardAwareScrollView scroll Input without extra scrolling Input up
Current workaround: use onLayout on View under KeyboardAwareScrollView
WITH WORKAROUND:
Screen.Recording.2023-03-17.at.19.13.03.mov
UPD: I believe this PR should fix this issue - #426
The text was updated successfully, but these errors were encountered: