IssueTracker

There is any solution??

Reproduced on a Nexus S. Very embarrassing issue for some webapps.

Note that an equivalent issue affects TimePickerDialog as well. I've confirmed that onTimeSet() gets called twice on pressing Done, and once if the dialog is closed with Back.

There are many ways to bypass this bug, i only posted it to let google know that there is a bug.

I have written some fix for this bug using js.

Available at stackoverflow

http://stackoverflow.com/a/11767743

[Comment deleted]

The js fix does not work for me. I tried totally removing the maxlength attr and commented out all existing javascript bindings and nothing helps. For me the maxlength does not seem to matter. Within a web-view on Jelly Bean I just cannot edit more then one text field. Even worse if I click a select in the form and then tap on a text field again I cannot get the keyboard back.

My Enyo and JQueryMobile text inputs won't work at all on JellyBean! Using AOKP custom ROM for HTC One S.

This is a major issue.  I am both an Android 4.1.1 user and a Web Developer.  I've hit this issue while doing development and I also browsed around to see if my site was the only one.  I was able to reproduce the issue on major sites like amazon.com.  This should be a very high priority for the .2 version since it was not been fixed in .1 and it literally locks your keyboard out of any html fields until you shutdown the browser and relaunch it.

I can confirm this on a Galaxy Nexus running 4.1.2

This bug has been reported for 3 months. As it occurs :
- on every tested devices (>4.1.1)
- everytime a maxlength attribute is used on a web page / webapp (which is quite often)
- the user has to restart completely its browser

I think the "medium" priority is not really appropriate

[Comment deleted]

Please note that this happens under Android 2.3 too when using an alternative soft-keyboard such as Swift Key.
Using the native keyboard under 2.3 the problem is not that big. You CAN seemingly enter too many characters, which won't show up in the input field and which you can delete again too. So, no complete crashes.

Under 4.1 you have to kill the browser task in order to be able to enter text again.
Reloading the page is NOT enough.

I'm designing medical apps for Android and this has been a huge pain to me. There's a stopgap solution on StackOverflow but it's ridiculous that I have to worry about having that script attached to every one of my pages.

I agree that "medium" is not appropriate as a priority. It took me hours to figure out that it was the maxlength attribute that caused this issue, and now I waste time whenever one of my pages crashes making sure that the fix is actually being applied.

This certainly is a developer's nightmare bug :)
Until you realize the root cause and feel the "ahaaa..." moment.
FYI: Even though all the input fields in the DOM freeze because of this bug, I was still able to manipulate and change values of the input fields using Javascript.

Any chance of a link to the StackOverflow workaround?
Also, what is the "ahaaa..." moment?
Thanks!

I, too, spent days finding the exact cause.  I found a solution as well:  you need to bind to the keypress event (haven't tried with keyup or keydown, but that might work as well) and remove the maxlength attribute.  Our solution was to add a data-xxx attribute and control the length within the event handler.  We were already doing that, but as long as the maxlength is there and too many keystrokes are entered, it locks key input:  Not just on the page, but the whole window (I navigated, in the same window, to Google and couldn't enter keystrokes).

The 'ahaaa...' moment is pretty clear, after trying for days to find the exact cause, then feeling elated because there actually is a solution (even if it's just to compensate for the 4.1.2 bug).  Isolating the cause can be quite frustrating when you're working with a complex site (and who would guess the 'maxlength' attribute was the culprit?).

Funny thing is that Samsung 4.1.2 devices DON'T exhibit this bug, but it shows up on several Motorola devices (and also the emulator).

Hi,

Provide the permission as   <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" /> in android Manifest file.

Now in my android 4.1.2 is working with acceptance input type number 7.

My quick workaround...
http://jsfiddle.net/LcqC9 .Tested on Chrome on Nexus 7 without issue)

I am also facing this issue in Android Browser..Is there any meta tag for solved this issue,i am not interest to use js...
I hope you can help me...Thanking you!...

We are facing the same issue. Does anyone have any solutions on JB?

There are a few solutions on Stack Overflow and JS Fiddle...
Here's one I've developed;
<input type="text" onKeyDown="if(this.value.length==8) this.value = this.value.slice(0, -1);">
Just change ==8 to =='n' where 'n' is the number of characters you need.
http://jsfiddle.net/u3Ltb6s2/

OnChange will only 'fire' if you click outside the text box. So AFAIK you cannot use OnChange.

I see.
Well I'll use OnKeyDown.
Thank you for helping me.

Is no one investigating this?  This appears to be an issue still on the Chrome 37 on Samsung S5 Android KitKat.

Now on Chrome WebView

Hello Android....
When will the legendary bug be fixed ??
Its still in present in the current OS version.

maxLength still isn't work properly on Android 5.0.1

[Comment deleted]

This has just been 'released' ? So what version Android will actually include this? 5.0 or higher?

Yes, the fix for this is included in Android 5.0 which has just been released to AOSP.

Will the fix be in support library?

There are currently no plans to move the DatePickerDialog to appcompat, but I wouldn't rule it out in the future.

Is this DatePickerDialog malfunction fixed on android 4.4.4 Nexus ?
Because I am not able to see this issue on android 4.4.4 Nexus whereas I was able to see it on android 4.4.2 version.

I have face similar issue and solve using int callCount=0; flag. Actually onDateSet is called twice in click.
// Update callCount=0 when click on button to change the date.

  callCount = 0;
if (callCount == 0) {
            datePickerDialog = new DatePickerDialog(this,
                    new DatePickerDialog.OnDateSetListener() {
                        @Override
                        public void onDateSet(DatePicker view, final int year, final int monthOfYear, final int dayOfMonth) {
                            callCount++;
                            // Get Current Time
                           .... // other code
                                TimePicker(year, monthOfYear, dayOfMonth); // is my time picker dialog

                            }
                        }
                    }, cYear, cMonth, cDay);

            datePickerDialog.show();
        }  

This worked for me.

Hemm conectid

Any updates on this? Still facing it on android 4.4

still the same bug

Thank you for the feedback. We're closing this issue as Obsolete.
If it is still observed in the latest Android release, please open a new issue in https://goo.gl/TbMiIO along with a reference to this issue.