Inputmask: On Android with date mask input mashing up

Created on 3 Oct 2017  Â·  16Comments  Â·  Source: RobinHerbots/Inputmask

When day typed and start typing month numbers mashing up:
https://jsfiddle.net/cp3cunm0/9/

When i try type: 13061985 ive got: 13/01/2050

Android Dates Enhancement / Feature Life example included => priority Main

Most helpful comment

This is a bug within the checkval fn. This will be fixed in version 4.x

All 16 comments

+1

The issue seems to be caused by the fact the position of the forward slashes aren't ignored by the caret positioning. So what happens is:

  1. You type 13, normally the caret should now be positioned after the first forward slash (this is not the case)
  2. You type in 06, but the caret is now positioned between the 0 and 6
  3. Typing in 1 next overwrites the 6, so you'll end up with 13/01
  4. Inputting the rest of the year results in 2050. I'm not entirely sure what exactly's happening there, but it may well be related to the previous.

This is a bug within the checkval fn. This will be fixed in version 4.x

Hi Robin, thanks for this library. It's great!

I just ran into the same issue, and am wondering if this is a regression I can work around with an earlier version or something I'll have to wait for the 4.x to use.

Thanks again.

Anyone have a work-around? Just started digging into this as it's holding up a big release for us. Don't really want to drop the library but it might come to that.

I will have a look tonight

On the 4.x branch Backspace works for the datemask. This evening i investigate the wrong caret positioning on Android for the datemask.

Normal input should work in the 4.x branch. Todo is review backspaces

Backspace ok.
Todo See #1713

Damn, the fix for the Backspace causes a regression in the input. => is was due to requesting the desktop mode of the page!!

There should be a reliable way to detect if it is android even if the desktop page mode is selected, ...

Detecting wheter the touchstart event is supported can be used to detect a "non desktop device" ;-)

@unbreak, @kwadrax, @thomaux, @madelynkasula , @camj256,

New jsfiddle (3.x) for testing

https://jsfiddle.net/cp3cunm0/11/

Still broke the exact same way on my v20. Android 7.0 and chrome.

On Oct 8, 2017 4:26 PM, "Robin Herbots" notifications@github.com wrote:

New jsfiddle for testing

https://jsfiddle.net/cp3cunm0/11/

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/RobinHerbots/Inputmask/issues/1708#issuecomment-335039804,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF82zVNvzE8ClEVWr3lsIwi1CD79ylPiks5sqT4WgaJpZM4Pr_FO
.

@camj256 ,

So you tested with https://jsfiddle.net/cp3cunm0/11/ ?

What exactly did you type? Which keyboard where you using? Can you do some debugging to see that the device is detected as a mobile one (by the inputmask)?

I tested on 3 tablets and 2 phones (android 6) and also on browserstack (android 7).
Can you reproduce the error on browserstack?

Can someone else also confirm?

@RobinHerbots, On my device (Nexus 5x, android 8, chrome, stack keyboard gboard) linked jsfiddle works fine!

Oh so sorry guys. Its working fine. I'm used to mm/dd format and wasnt
paying attention last night. Its looking good!

On Oct 9, 2017 3:11 AM, "unbreak" notifications@github.com wrote:

@RobinHerbots https://github.com/robinherbots, On my device (Nexus 5x,
android 8, chrome, stack keyboard gboard) jsfiddle works fine!

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/RobinHerbots/Inputmask/issues/1708#issuecomment-335090440,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF82zSPE3GKcOMsokIWFeFrNWma61kL6ks5sqdVNgaJpZM4Pr_FO
.

This issue can be xlosed?

Was this page helpful?
0 / 5 - 0 ratings