Bug 18166 - Next/Done button on soft numeric keypad showing Next when Done should be displayed.
Summary: Next/Done button on soft numeric keypad showing Next when Done should be disp...
Status: CONFIRMED
Alias: None
Product: Android
Classification: Xamarin
Component: General (show other bugs)
Version: 4.12.0
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Jonathan Pryor
URL:
Depends on:
Blocks:
 
Reported: 2014-03-04 15:32 UTC by Jon Goldberger [MSFT]
Modified: 2014-03-05 13:18 UTC (History)
3 users (show)

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


Attachments
Test Project (26.43 KB, application/zip)
2014-03-04 15:34 UTC, Jon Goldberger [MSFT]
Details
Screen Shots of error (63.39 KB, application/zip)
2014-03-04 15:35 UTC, Jon Goldberger [MSFT]
Details
Version info (3.28 KB, text/plain)
2014-03-04 15:36 UTC, Jon Goldberger [MSFT]
Details

Comment 1 Jon Goldberger [MSFT] 2014-03-04 15:34:36 UTC
From case:
I have a small problem. Maybe you could see if you find the problem 
behind this.

I have a ListView and two EditTexts (both numeric). The first time I go 
through the EditTexts I get the correct "Done" Button in my keyboard 
(see screenshot "FirstTime.png", Fertig means Done in German). Then I 
insert an item in the ListView and update the DataSet with the command 
NotifyDataSetChanged();.

When I go through my EditTexts for the second time I get the wrong 
"Next" Button. This is wrong because no third input control follows 
after editText2. There should be the correct "Done" Button like I got 
the first time. (see screenshot "SecondTime.png", Weiter means Next in 
German).

Please find the info about VS, the screenshots and a test case in the 
attachment.
--------------------------------------------------
Update: I just realized that the problem is android version specific. If
I change the target android version to level 14+ instead of something
below, the problem won't occur anymore.
---------------------------------------------------
Update to my last mail. The change to android version 14+ doesn't
entirely solve the issue. For me it's just working in my test case. But
in my real customer project the problem still exists. (I don't know in
which way the projects actually differ)

If I comment out this line:
NotifyDataSetChanged();
everything works normal. But I do need this call.
Sorry, I know, this is getting really strange now.
---------------------------------------------------
Comment 2 Jon Goldberger [MSFT] 2014-03-04 15:34:59 UTC
Created attachment 6217 [details]
Test Project
Comment 3 Jon Goldberger [MSFT] 2014-03-04 15:35:49 UTC
Created attachment 6218 [details]
Screen Shots of error
Comment 4 Jon Goldberger [MSFT] 2014-03-04 15:36:14 UTC
Created attachment 6219 [details]
Version info
Comment 5 Jon Goldberger [MSFT] 2014-03-04 15:37:26 UTC
I  was able to replicate the issue on emulators. Here are my findings:

Issue does not occur on my Galaxy Tab 2 running Android 4.2.2 (API 17) with original project settings, targeting API 8, compile using API 8, Minimum target API 8.
API_15 emulator (Android vers. 4.1.1) issue occurred with original project settings, commenting out NotifyDataSetChanged() did not fix issue. Changing target API to 14 or 15 as mentioned did not fix issue either.
API_16 emulator: Issue occurred with target platform set to API 8, but not with target platform set to API 14, 15 or 16.
API_17 emulator: Issue occurred with target platform set to API 8, but not with target platform set to API 14, 15 or 16.

Now this is odd that I got the issue on the API 17 emulator, but not on my API 17 device testing all of the above target platforms, 8 14, 15, and 16.
Comment 6 Ram Chandra 2014-03-05 13:18:08 UTC
I tried to reproduce this issue with "attached project" and i am able to reproduce this issue. But when I try to debug "attached project" on API_16 and API_17 emulator i have found same behavior on both emulator and same issue occurred with target platform set to API 8 as well as with target platform set to API 14, 15 or 16.

Commented out NotifyDataSetChanged() also did not fix issue either.

Screencast: http://www.screencast.com/t/77P8nVN4

Environment:

Windows 7
VS2013
xamarin.Android : 4.12.00028

Note You need to log in before you can comment on or make changes to this bug.