You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 1, 2024. It is now read-only.
Any Xamarin Forms application installed on iPhone, with many text entries in the ListView.
Any Xamarin Forms application installed on iPhone, with many text entries in the CollectionView.
Expected Behavior
Like Android keyboard, having a Next button in the keyboard on iPhone, in Xamarin Forms apps, to shift the focus from one entry to the next entry in the list.
Actual Behavior
No Next button available in the default iPhone keyboard to navigate the focus from one text entry to the next entry in the list.
Basic Information
Version with issue:
Last known good version:
Platform Target Frameworks:
iOS: 11.1
Android: 13.1
NuGet Packages:
Affected Devices: All iPhones
Environment
All Environments
Build Logs
No issues with builds
-->
The text was updated successfully, but these errors were encountered:
You can set ReturnType="Next" on the Entry, I hope that this doesn't only show it visually but will also allow you to hop to the next Entry. If not, here is some code that might be able to help you with that.
Unfortunately at this point in the Xamarin.Forms lifecycle we won't be implementing anything new to support this. You should be able to make this work yourself with a plugin or custom renderer.
Description
Next button in the keyboard on iPhones.
Steps to Reproduce
Expected Behavior
Like Android keyboard, having a Next button in the keyboard on iPhone, in Xamarin Forms apps, to shift the focus from one entry to the next entry in the list.
Actual Behavior
No Next button available in the default iPhone keyboard to navigate the focus from one text entry to the next entry in the list.
Basic Information
Environment
All Environments
Build Logs
No issues with builds
-->
The text was updated successfully, but these errors were encountered: