Bug 41560 - Xamarin Forms Editor: Unable to enter consecutive numbers in Android
Summary: Xamarin Forms Editor: Unable to enter consecutive numbers in Android
Status: RESOLVED NORESPONSE
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 1.2.2
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Rui Marinho
URL:
Depends on:
Blocks:
 
Reported: 2016-06-07 14:20 UTC by ernest.james
Modified: 2017-06-19 18:30 UTC (History)
6 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED NORESPONSE

Description ernest.james 2016-06-07 14:20:51 UTC
1.	Place Editor in xaml page
2.	Set keyboard to  Keyboard.Create(KeyboardFlags.CapitalizeSentence)
3.	Run program in android
4.	Click on editor. Keyboard appears.
5.	Type some characters. (optional)
6.	Click on “123” button.
7.	Type a number.
8.	Keyboard flips back to alpha keyboard. 
9.	To type another number you must click on “123”

Expected Result: Should stay on numbers until user selects “abc”
Comment 1 Rui Marinho 2016-06-29 11:09:49 UTC
Thank you for taking the time to submit the bug. We tried to reproduce the issue you reported but were unable given the description. We used the last version of Xamarin.Forms 2.3.0.

If you could please attach a reproduction to the bug by starting with a clean Xamarin.Forms project and adding just the code necessary to demonstrate the issue, we would very much appreciate it. 

For your convenience, we have created some reproduction best practices viewable here: https://gist.github.com/jassmith/92405c300e54a01dcc6d

Warm regards,
Xamarin Forms Team
Comment 2 Samantha Houts [MSFT] 2017-06-19 18:30:02 UTC
Because we have not received a reply to our request for more information we are closing this issue. If you are still encountering this issue, please reopen the ticket with the requested information. Thanks!