Keyboard keeps showing on Android emulator even when new page navigated to

Question

Keyboard keeps showing on Android emulator even when new page navigated to

Lloyd Sheen 1,486

I have a search page. When I input into an Entry control and the lenght of the input is greater than 2 I query a service which gives me a list of things that partialy match the input. This list is then provided to a CollectionView to show. The problem is that the keyboard does not disappear as it did in Xamarin. To get rid of it on emulator I have to click the keyboard selection button and then select the keyboard and then it disappears.

Lloyd Sheen 1,486 Reputation points

2023-02-06T15:04:29.18+00:00
I have no idea whether you will see my edits (Hey MS fix this horrible site). I made them but cannot see them. Why is this site allowed to continue with such problems????

The addition to the above (maybe) is:

I have a search page. When I input into an Entry control and the lenght of the input is greater than 2 I query a service which gives me a list of things that partialy match the input. This list is then provided to a CollectionView to show. The problem is that the keyboard does not disappear as it did in Xamarin. To get rid of it on emulator I have to click the keyboard selection button and then select the keyboard and then it disappears.

Now there is something that I think is related to this problem. When I am inputing and it does a query and gets results it does not show them. The code used is as follows:

<CollectionView Grid.Row="2" ItemsSource="{Binding players}" BackgroundColor="Yellow"> <CollectionView.ItemsLayout> <GridItemsLayout Orientation="Vertical" Span="2"/> </CollectionView.ItemsLayout> <CollectionView.ItemTemplate> <DataTemplate> <Label Text="{Binding playerName}"> <Label.GestureRecognizers> <TapGestureRecognizer NumberOfTapsRequired="2" Tapped="showPlayer"></TapGestureRecognizer> </Label.GestureRecognizers> </Label> </DataTemplate> </CollectionView.ItemTemplate> </CollectionView> The code behind is : private List<playerInfo> _players; public List<playerInfo> players { get { return _players; } set { _players = value; //thePlayerList.ItemsSource = value; RaiseChanged("players"); } }

Now when I use the binding for the ItemsSource nothing is shown. The BindingContext is set to this (simple page) in the constructor. When I change the code to use the non-binding version of CollectionView and set the ItemsSource manually it then shows the list. This is beyond confusing as binding is usually very simple.
Yonglun Liu (Shanghai Wicresoft Co,.Ltd.) 50,126 Reputation points Microsoft External Staff

2023-02-21T07:56:34.07+00:00
The problem is that the keyboard does not disappear as it did in Xamarin.

Could you please provide more detailed information about the platform your program runs on and the API level?

You could use the native platform's code to manually make the soft keyboard disappear.

Now when I use the binding for the ItemsSource nothing is shown. The BindingContext is set to this (simple page) in the constructor.

After my tests, the data binding still works after setting bindingcontext to this, here is my code:

public partial class NewPage1 : ContentPage { private List<Playerinfo> _players; public List<Playerinfo> players { get { return _players; } set { _players = value; } } public NewPage1() { InitializeComponent(); players = new List<Playerinfo>(); players.Add(new Playerinfo { playerName = "test0" }); players.Add(new Playerinfo { playerName = "test1" }); players.Add(new Playerinfo { playerName = "test2" }); players.Add(new Playerinfo { playerName = "test3" }); BindingContext = this; } }

For further investigation, could you please provide a minimized example that reproduces this issue?

It would be helpful for us to find the real cause.

1 answer

Your answer

Lloyd Sheen 1,486 Reputation points

2023-02-06T15:04:29.18+00:00

I have no idea whether you will see my edits (Hey MS fix this horrible site). I made them but cannot see them. Why is this site allowed to continue with such problems????

The addition to the above (maybe) is:

I have a search page. When I input into an Entry control and the lenght of the input is greater than 2 I query a service which gives me a list of things that partialy match the input. This list is then provided to a CollectionView to show. The problem is that the keyboard does not disappear as it did in Xamarin. To get rid of it on emulator I have to click the keyboard selection button and then select the keyboard and then it disappears.

Now there is something that I think is related to this problem. When I am inputing and it does a query and gets results it does not show them. The code used is as follows:

<CollectionView Grid.Row="2" ItemsSource="{Binding players}" BackgroundColor="Yellow"> <CollectionView.ItemsLayout> <GridItemsLayout Orientation="Vertical" Span="2"/> </CollectionView.ItemsLayout> <CollectionView.ItemTemplate> <DataTemplate> <Label Text="{Binding playerName}"> <Label.GestureRecognizers> <TapGestureRecognizer NumberOfTapsRequired="2" Tapped="showPlayer"></TapGestureRecognizer> </Label.GestureRecognizers> </Label> </DataTemplate> </CollectionView.ItemTemplate> </CollectionView> The code behind is : private List<playerInfo> _players; public List<playerInfo> players { get { return _players; } set { _players = value; //thePlayerList.ItemsSource = value; RaiseChanged("players"); } }

Now when I use the binding for the ItemsSource nothing is shown. The BindingContext is set to this (simple page) in the constructor. When I change the code to use the non-binding version of CollectionView and set the ItemsSource manually it then shows the list. This is beyond confusing as binding is usually very simple.
Yonglun Liu (Shanghai Wicresoft Co,.Ltd.) 50,126 Reputation points Microsoft External Staff

2023-02-21T07:56:34.07+00:00

The problem is that the keyboard does not disappear as it did in Xamarin.

Could you please provide more detailed information about the platform your program runs on and the API level?

You could use the native platform's code to manually make the soft keyboard disappear.

Now when I use the binding for the ItemsSource nothing is shown. The BindingContext is set to this (simple page) in the constructor.

After my tests, the data binding still works after setting bindingcontext to this, here is my code:

public partial class NewPage1 : ContentPage { private List<Playerinfo> _players; public List<Playerinfo> players { get { return _players; } set { _players = value; } } public NewPage1() { InitializeComponent(); players = new List<Playerinfo>(); players.Add(new Playerinfo { playerName = "test0" }); players.Add(new Playerinfo { playerName = "test1" }); players.Add(new Playerinfo { playerName = "test2" }); players.Add(new Playerinfo { playerName = "test3" }); BindingContext = this; } }

For further investigation, could you please provide a minimized example that reproduces this issue?

It would be helpful for us to find the real cause.

Answer 1

Lloyd Sheen 1,486

I had forgotten about this post. I found the following code which I use when the new page is navigated to, but still does not explain why Xamarin closes the keyboard and Maui does not:

    public void HideKeyboard()
    {
        var context = Android.App.Application.Context;
        var inputMethodManager = context.GetSystemService(Context.InputMethodService) as InputMethodManager;
        if (inputMethodManager != null)
        {
            var activity = Platform.CurrentActivity;
            var token = activity.CurrentFocus?.WindowToken;
            inputMethodManager.HideSoftInputFromWindow(token, HideSoftInputFlags.None);
            activity.Window.DecorView.ClearFocus();
        }

    }

Yonglun Liu (Shanghai Wicresoft Co,.Ltd.) 50,126 Reputation points Microsoft External Staff

2023-02-22T08:06:20.3233333+00:00

I found the following code which I use when the new page is navigated to, but still does not explain why Xamarin closes the keyboard and Maui does not:

Thanks for your feedback.

For issues where the same code behaves differently in Xamarin and MAUI, it is recommended that you submit feedback in GitHub maui-issues to make our product group aware of it.

You could refer to this documentation Creating an issue to get detailed steps.

Share via

Keyboard keeps showing on Android emulator even when new page navigated to

1 answer

Your answer