- Home
- Forum
- Xamarin.Forms
- [Android] UI autoresize doesnt keep keyboard opened if inside SfTabItem
[Android] UI autoresize doesnt keep keyboard opened if inside SfTabItem
Good afternoon,
Attachment: 20191118_160808_5aa34b26.7z
i have a SfTextInputLayout inside a SfCard, if i enable the android auto resize if there isn't enough space for the keyboard using the following line:
Xamarin.Forms.Application.Current.On<Xamarin.Forms.PlatformConfiguration.Android>().UseWindowSoftInputModeAdjust(WindowSoftInputModeAdjust.Resize);
the keyboard keeps autoclosing and the user doesn't have the time to write.
My xaml code of the View:
<ScrollView Padding="16">
<StackLayout>
<sfCards:SfCardView SwipeToDismiss="False" Margin="0,20,0,0" HorizontalOptions="Center" WidthRequest="500">
<StackLayout Padding="16">
<Label x:Name="label_SfCardView_NewDatabase_Title"/>
<sfTextInputLayout:SfTextInputLayout x:Name="sfTextInputLayout_SfCardView_NewDatabase_DatabaseName" ContainerType="Outlined" OutlineCornerRadius="5" ReserveSpaceForAssistiveLabels="True" FocusedColor="#007bff" ErrorColor="#dc3545">
<Entry x:Name="entry_SfCardView_NewDatabase_DatabaseName"/>
</sfTextInputLayout:SfTextInputLayout>
<sfTextInputLayout:SfTextInputLayout x:Name="sfTextInputLayout_SfCardView_NewDatabase_DatabasePath" ContainerType="Outlined" OutlineCornerRadius="5" ReserveSpaceForAssistiveLabels="False" FocusedColor="#007bff" ErrorColor="#dc3545" LeadingViewPosition="Inside" IsVisible="False">
<sfTextInputLayout:SfTextInputLayout.LeadingView>
<ImageButton x:Name="imageButton_SfCardView_NewDatabase_BrowseFolder" HeightRequest="20" Aspect="AspectFit" Source="glyphicons_145_folder_open.png" Clicked="ImageButton_SfCardView_NewDatabase_BrowseFolder_Clicked"/>
</sfTextInputLayout:SfTextInputLayout.LeadingView>
<Editor x:Name="editor_SfCardView_NewDatabase_DatabasePath" IsEnabled="False" AutoSize="TextChanges"/>
</sfTextInputLayout:SfTextInputLayout>
<sfButtons:SfButton x:Name="sfButton_SfCardView_NewDatabase_Confirm" Margin="0,16" CornerRadius="5" HeightRequest="40" BackgroundColor="#007bff" Clicked="SfButton_SfCardView_NewDatabase_Confirm_Clicked" Text="Confirm"/>
</StackLayout>
</sfCards:SfCardView>
</StackLayout>
</ScrollView>
is a view inside a Grid in a SfNavigationDrawer inside a SfTabItem:
<sfTabView:SfTabItem.Content>
<sfNavigationDrawer:SfNavigationDrawer x:Name="sfNavigationDrawer_Database" BackgroundColor="White" TouchThreshold="50" DrawerHeaderHeight="50" DrawerFooterHeight="0" Duration="200" Position="Left" Transition="SlideOnTop" EnableSwipeGesture="False">
<sfNavigationDrawer:SfNavigationDrawer.ContentView>
<Grid BackgroundColor="White">
<Grid.RowDefinitions>
<RowDefinition Height="Auto"/>
<RowDefinition/>
</Grid.RowDefinitions>
<StackLayout BackgroundColor="#1aa1d6" Orientation="Horizontal" HeightRequest="50">
<Image StyleId="image_Database_Hamburger" HeightRequest="40" Aspect="AspectFit" HorizontalOptions="Center" VerticalOptions="Center" WidthRequest="40" Source="glyphicons_517_menu_hamburger.png" Margin="10,0,0,0">
<Image.GestureRecognizers>
<TapGestureRecognizer Tapped="Image_Database_Hamburger_Tapped" />
</Image.GestureRecognizers>
</Image>
<Label x:Name="label_Database_ViewCaption" HeightRequest="50" HorizontalTextAlignment="Center" VerticalTextAlignment="Center" FontSize="16" TextColor="White"/>
</StackLayout>
<Grid x:Name="grid_SfNavigationDrawer_Database_Content" Grid.Row="1"></Grid>
</Grid>
</sfNavigationDrawer:SfNavigationDrawer.ContentView>
........................
You can find a video attached.
Thanks in advance
Attachment: 20191118_160808_5aa34b26.7z
SIGN IN To post a reply.
7 Replies
RA
Rachel A
Syncfusion Team
November 19, 2019 08:51 AM UTC
Hi Marco,
Greetings from Syncfusion.
We have checked the reported issue "UI auto resize doesn’t keep keyboard opened, if placed inside the SfNavigationDrawer" and we have already logged a bug report for this, and it can be tracked through our feedback portal below.
Link: https://www.syncfusion.com/feedback/7168/android-entry-get-unfocused-when-resize-the-navigationdrawer-size-based-on
Please cast your vote to make it count. We are facing the architecture level complexity. So, based on the prioritization we will include the changes in any of the upcoming release.
Link: https://www.syncfusion.com/feedback/7168/android-entry-get-unfocused-when-resize-the-navigationdrawer-size-based-on
Please cast your vote to make it count. We are facing the architecture level complexity. So, based on the prioritization we will include the changes in any of the upcoming release.
Thanks,
Rachel.
Hi Marco,Greetings from Syncfusion.We have checked the reported issue "UI auto resize doesn’t keep keyboard opened, if placed inside the SfNavigationDrawer" and we have already logged a bug report for this, and it can be tracked through our feedback portal below.
Link: https://www.syncfusion.com/feedback/7168/android-entry-get-unfocused-when-resize-the-navigationdrawer-size-based-on
Please cast your vote to make it count. We are facing the architecture level complexity. So, based on the prioritization we will include the changes in any of the upcoming release.Thanks,Rachel.
I voted, but few peoples voted two times decreasing the votes.
We made an entire application inside NavigationDrawers, it's very important for us.
Thanks in advance
RA
Rachel A
Syncfusion Team
November 20, 2019 01:37 PM UTC
Hi Marco,
As we are facing the architecture level complexity, we require timeline to check the feasibility in the source and update you further information on 26th November 2019.
Appreciate your patience until then.
Thanks,
Rachel.
RA
Rachel A
Syncfusion Team
November 26, 2019 10:11 AM UTC
Hi Marco,
The mentioned issue fix will be included in the upcoming release of Volume 4 which will be available by the mid-December 2019.
Thanks,
Rachel.
Hi Marco,The mentioned issue fix will be included in the upcoming release of Volume 4 which will be available by the mid-December 2019.Thanks,Rachel.
Thanks for the fix
RA
Rachel A
Syncfusion Team
December 30, 2019 10:00 AM UTC
Hi Marco,
Thank you for confirming that the issue has been resolved.
Regards,
Rachel.
Hi Marco,Thank you for confirming that the issue has been resolved.Regards,Rachel.
I was wrong, the issue still exists in the last version 17.4.0.41
SIGN IN To post a reply.
- 7 Replies
- 2 Participants
-
MN Marco Negroni
- Nov 18, 2019 03:09 PM UTC
- Jan 13, 2020 02:24 PM UTC