One of our customer is facing issue with InputType when using ViewPage and EditText
I've got this app with multiple fragments in a viewpager. These fragments all show an EditText, most of them having inputtype numberDecimal, three of them having no inputtype specified.
Outside this viewpager there is another edittext which serves as searchbox.
I've done some manual focusing inside the touch event of the EditText to gain the right EditText focus inside the viewpager. (because of an issue similar to the one described here: [ViewPager focus issue])
When I select the first EditText in my ViewPager, the right keyboard type shows up (nummeric). Now when I choose the next EditText the default keyboard shows up while having specified inpytType numberDecimal.
When I remove the (search) EditText outside the viewPager and repeat the above scenario, the second EditText does get the correct keyboardtype.
To me it almost looks like the search EditText is stealing focus somehow from the EditText inside my Fragment that's inside the viewpager.
How can I prevent it from doing this?
I already gave it's parent the android:focusableInTouchMode="true" property.
I’m using Visual Studio 2012 update 4 and Xamarin 184.108.40.206 and Xamarin.Android 220.127.116.11
### Sample Project
Issue appears when selecting the first EditText in the ViewPager and after that selecting the second one. A alphanumeric keyboard appears while this particular EditText has set it's inputType to number.
Issue only appears on an actual device, not in the emulator/Xamarin Android Player.
I have checked this issue and able to reproduce this. To reproduce this issue I have followed the steps and instruction provided in bug description.
Steps I followed:
1. Open attached test case in VS.
2. Deploy it on android device.
3. Select first EditText in the ViewPager
4. Observe that nummeric keyboard shows up.
5. Choose the next EditText.
6. Observed that the default keyboard(alphanumeric ) shows.
Screencast(Device Pic): http://www.screencast.com/t/X5dUJmWs
VS Trace Logs: https://gist.github.com/Rajneesh360Logica/1d63404d9ea44ef1f97d
Device Logs(XAP): https://gist.github.com/Rajneesh360Logica/a00e97f28aef1d13442f
Device Log(Nexus 5):
Microsoft Visual Studio Professional 2013
Version 12.0.30723.00 Update 3
Microsoft .NET Framework
Installed Version: Professional
LightSwitch for Visual Studio 2013 06177-004-0446016-02381
Microsoft LightSwitch for Visual Studio 2013
Team Explorer for Visual Studio 2013 06177-004-0446016-02381
Microsoft Team Explorer for Visual Studio 2013
Visual Basic 2013 06177-004-0446016-02381
Microsoft Visual Basic 2013
Visual C# 2013 06177-004-0446016-02381
Microsoft Visual C# 2013
Visual C++ 2013 06177-004-0446016-02381
Microsoft Visual C++ 2013
Visual F# 2013 06177-004-0446016-02381
Microsoft Visual F# 2013
Visual Studio 2013 Code Analysis Spell Checker 06177-004-0446016-02381
Microsoft® Visual Studio® 2013 Code Analysis Spell Checker
Portions of International CorrectSpell™ spelling correction system © 1993 by Lernout & Hauspie Speech Products N.V. All rights reserved.
The American Heritage® Dictionary of the English Language, Third Edition Copyright © 1992 Houghton Mifflin Company. Electronic version licensed from Lernout & Hauspie Speech Products N.V. All rights reserved.
Windows Phone SDK 8.0 - ENU 06177-004-0446016-02381
Windows Phone SDK 8.0 - ENU
Application Insights Tools for Visual Studio Package 1.0
Application Insights Tools for Visual Studio
ASP.NET and Web Tools 12.3.50717.0
Microsoft Web Developer Tools contains the following components:
Support for creating and opening ASP.NET web projects
Browser Link: A communication channel between Visual Studio and browsers
Page Inspector: Inspection tool for ASP.NET web projects
Scaffolding: A framework for building and running code generators
Server Explorer extensions for Microsoft Azure Websites
Web publishing: Extensions for publishing ASP.NET web projects to hosting providers, on-premises servers, or Microsoft Azure
ASP.NET Web Frameworks and Tools 2012.2 4.1.21001.0
For additional information, visit http://go.microsoft.com/fwlink/?LinkID=309563
ASP.NET Web Frameworks and Tools 2013 5.2.20703.0
For additional information, visit http://www.asp.net/
Common Azure Tools 1.2
Provides common services for use by Azure Mobile Services and Microsoft Azure Tools.
Microsoft Advertising SDK for Windows Phone
Microsoft Advertising SDK for Windows Phone
Microsoft Azure Mobile Services Tools 1.2
Microsoft Azure Mobile Services Tools
NuGet Package Manager 2.8.50926.663
NuGet Package Manager in Visual Studio. For more information about NuGet, visit http://docs.nuget.org/.
Office Developer Tools for Visual Studio 2013 ENU 12.0.30626
Microsoft Office Developer Tools for Visual Studio 2013 ENU
PowerShell Tools 1.2
Provides file classification services using PowerShell
PreEmptive Analytics Visualizer 1.2
Microsoft Visual Studio extension to visualize aggregated summaries from the PreEmptive Analytics product.
SQL Server Data Tools 12.0.30919.1
Microsoft SQL Server Data Tools
Windows Phone 8.1 SDK Integration 1.0
This package integrates the tools for the Windows Phone 8.1 SDK into the menus and controls of Visual Studio.
Workflow Manager Tools 1.0 1.0
This package contains the necessary Visual Studio integration components for Workflow Manager.
Xamarin 3.9.340.0 (8e87bcf)
Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.
Xamarin.Android 18.104.22.168 (49a04b966feb40dfdba49d57ba16249b66d606a6)
Visual Studio plugin to enable development for Xamarin.Android.
Xamarin.iOS 22.214.171.124 (862702c6b8aa14a373e25f83ac45918556af41a2)
Visual Studio extension to enable development for Xamarin.iOS.
Xamarin.iOS Unified Migration 1.0
Automated migration for Xamarin iOS Classic projects to Unified
Any idea when we can expect a solution or when you have time to look into this issue?
I'm not certain that this is a Xamarin.Android bug.
The way to verify would be to port the app to Java and see how the equivalent Java app behaves. I suspect that the issue is in the Android support library doing "something screwy"; my *guess* is that the android:inputType attribute is only honored when the view is *created*, and when you swap between the active EditText things go "weird."
Regardless, I don't see anything here that would suggest it's specific to Xamarin.Android issue and wouldn't also happen in Java.
Unfortunately I lack the time at this point to do the port to verify this.