Browsers on Android don't return keyCodes properly on the keydown event. about decimal-input

[jgkiano]

I've encountered this issue before but luckily I had rx included in the project. What I did was pipe changes from the input to a stream then run some validation and manipulate the typed data if required. Finally i'd bind the value of the input to the output of the stream. I'm not sure if this pattern will help you though. As far as I can remember this has always been an issue for android.

[jgkiano]

Cool, let me know if it works out.

…

On Tue, Jan 7, 2020, 7:47 AM KSHN ***@***.***> wrote: I've encountered this issue before but luckily I had rx included in the project. What I did was pipe changes from the input to a stream then run some validation and manipulate the typed data if required. Finally i'd bind the value of the input to the output of the stream. I'm not sure if this pattern will help you though. As far as I can remember this has always been an issue for android. I'll attempt a fix based on this and get back. Thank you — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACID5QSJQEY6PKMDQW7QXSTQ4QCOBANCNFSM4KBODNYQ> .

[malcolmkiano]

Instead of detecting keyCodes, passed old value and new value of inputs to a function to compare and determine the changes, then perform tasks based on the result of this.

[malcolmkiano]

I've encountered this issue before but luckily I had rx included in the project. What I did was pipe changes from the input to a stream then run some validation and manipulate the typed data if required. Finally i'd bind the value of the input to the output of the stream. I'm not sure if this pattern will help you though. As far as I can remember this has always been an issue for android.

I'll attempt a fix based on this and get back. Thank you