Repository navigation
Scroll list height doesn't get adjusted when the keyboard is visible #103
Description
Monday Jul 20, 2015 at 20:32 GMT
Originally opened as https://github.com/flutter/engine/issues/147
From @Hixie on April 21, 2015 19:28
Copied from original issue: domokit/mojo#106
Activity
FlutterIssues commentedon Nov 9, 2015
Monday Jul 20, 2015 at 20:32 GMT
From @jamesr on April 21, 2015 19:30
I think we're supposed to set android:windowSoftInputMode="adjustResize" in our AndroidManifest.xml and then respond to the view resizes that android generates for us
FlutterIssues commentedon Nov 9, 2015
Monday Jul 20, 2015 at 20:33 GMT
From @HansMuller on April 21, 2015 19:43
I've been testing against a version of Mojo with windowSoftInputMode="adjustResize". My app and the Sky stocks app work OK with this setting. In my case it's essential. I will submit a patch.
FlutterIssues commentedon Nov 9, 2015
Monday Jul 20, 2015 at 20:33 GMT
From @jamesr on April 21, 2015 19:52
That'd be great!
FlutterIssues commentedon Nov 9, 2015
Monday Jul 20, 2015 at 20:33 GMT
From @HansMuller on April 21, 2015 19:59
https://codereview.chromium.org/1056133007/
FlutterIssues commentedon Nov 9, 2015
Thursday Jul 23, 2015 at 20:17 GMT
@HansMuller can you resurrect that CL? Looks like we never actually checked that in.
FlutterIssues commentedon Nov 9, 2015
Friday Jul 24, 2015 at 16:44 GMT
android:windowSoftInputMode="adjustResize"
This is the change I made to cause the app to resize to make room for the virtual ("soft") keyboard:
https://codereview.chromium.org/1056133007/
It works nicely when the input box is at the bottom of the app, since the input box is very likely to remain visible after the resize.
Abnother project undid the change because the resize doesn't always leave the input box visible.
It's not entirely clear how we should be setting android:windowSoftInputMode. For example if an Input box is the child of a Scrollable, maybe it should just be scrolled into view - if that's necessary.
FlutterIssues commentedon Nov 9, 2015
Monday Jul 27, 2015 at 15:44 GMT
I'm not sure that change Hans linked to is quite right either. I tried to simply undo it in https://codereview.chromium.org/1249693004/ , but after an offline discussion, I suggested another approach in that patch. I probably won't have time to pursue it in the short term, but maybe the solution is reasonable?
/cc @qsr
Update arm64 toolchain to based on changes in flutter#93 (flutter#103)
github-actions commentedon Aug 17, 2021
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.