DataGrid Input field got hidden behind keyboard in SfTabview

[DEV]

Hi,

I'm having an issue with the component SfTabView on Android devices (we only use this plateform) :

•     ✅ Tab 1 Grid input field on tapping will trigger keyboard and push the field to appear above the keyboard.
•     ❌ Tab 2 Grid input field on tapping will trigger keyboard but it didn't push the field to appear above the keyboard causing it's not visible and hard for input to proceed.

This situation only happens if the DataGrid is inside the SfTabView and it's not in the first tab.

I'm using the SfTabView and SfDataGrid version 33.2.15 (also tried in version 28.1.33 and 33.1.15)

I've attached a project to illustrate my problem.

I also found this article, kindda same problem in Xamarin Forms, tried the workaround but didn't work either : https://www.syncfusion.com/forums/173099/entry-input-field-got-hidden-behind-keyboard-in-sftabview

PS : The TabView content is based on this article : https://support.syncfusion.com/kb/article/11416/how-to-load-a-content-page-into-a-tab-page-in-net-maui-tab-view

Thanks,

Kevin.

Attachment: MAUI.Syncfusion.TabView.Demo_9916d8d9.zip

[Tameem Ansari Yousoof Iqbal]

 Hi Kevin,

Greetings from Syncfusion support!

We would like to inform you that the issue originates from the .NET MAUI framework. Specifically, when using input controls that trigger the keyboard in the first tab of the TabView, the keyboard correctly avoids overlapping with the focused input control. However, in the second tab, the keyboard hides the focused entry.

In our scenario, we created a custom layout inside a grid based on the TabView layout. This layout includes a ContentView with multiple entries and two buttons that adjust the x-translation of the ContentView dynamically. The issue arises when the ContentView is translated to the right, the keyboard overlaps with it, causing usability problems.

We have already reported this bug to the .NET MAUI team, and we will update you as soon as we receive any feedback or fixes from their end.

Thank you for your understanding and patience.
 

For more details, please refer to the GitHub link below: 

Link : The keyboard overlaps with the Entry inside the ContentView when translating its x position to the …

 

Regards,

Tameem.