Xamarin.Forms
Xamarin.Forms copied to clipboard
(Android) Entry open keyboard pushes the shell tabbar up
Description
When I'm using WindowSoftInputModeAdjust.Resize bottom part of Shell (Tab Bar) appears just above the keyboard.
On iOS all working well, when I'm opening keyboard, all panels (navigation bar on the top of the screen and tab bar on the bottom) stay where they suppose to be, but page (loaded into Shell) scrolling up if it's needed when I'm opening keyboard.
Expected Behavior
What I want to see: the same behaviour for android and iOS (and it's should be like on iOS) or at least have some option to set such behaviour.
P.S. for iOS exists other problem, when you really need to resize whole app including tab bar. Lets say we have an app with chat-like page (we set Shell Tab Bar visibility to False and placed some Entry on the bottom of the screen), in this case WindowSoftInputModeAdjust.Resize solve the issue for Android, but for iOS we need to create some workaround code (there exists several typical solutions).
P.S.S. I'm have not so much experience in Xamarin development. Maybe solutions was already included in the latest versions of Xamarin.Forms?
@PureWeen We should align the behavior, right? What do you think the desired behavior should be?
Is there are any news?
No @maksym-husiev this is a known current issue but is prob not going to be fixed any time soon.
The only way to realy work around this is something like
Application.Current.On<Android>().UseWindowSoftInputModeAdjust(WindowSoftInputModeAdjust.Resize);
This will cause the Android application to resize the page rather than panning it up to make room.
But it has serious limitations if you are in a shell app.... god forbid a shell app with tabs
Other options are adding custom keyboards... and that is a whole slew of crazy.
Long story sort @samhouts if you have a list inside of scroll view (aka think of a forum) and you want a quick reply box at the bottom of the list... because of the fact that listview will just continue expanding forever on iOS ONLY the button could end up 37 fast swipes down the page...
It does not go by absolute values because 0100 or .5.5.5.5 is now 37 fast swipes away.
I do have a workaround on this with some funky dorry kerfufles. but requires doing some things... that really shouldn't be public :) but you can kinda sorta get it working with a custom renderer and setting l,t,r = 0 b= previousmargin.
Hey, I'm having the same issue. Seems like manifest settings
Xamarin.Forms 4.8.0.1560 Visual Studio for Mac 8.8 build 2913