Where :
the component is great for most of usage. The only issue I found is when I use it on an Android app.
How to reproduce it :
You need to use the component on a cordova app and run it on Android. The device must have a wedge scanner. ( I suppose this can be emulated with virtual keyboard ?!?! I am not an expert on Android at all )
What happens :
When adding debug in the component I noticed that keypress event won't give the correct e.which value. e.keyCode doesn't give anything useful either.
Looking on SO, I saw the following post that tells the story better than me.
The solution on this thread doesn't seem to work.. But I was hoping someone could assist me on this issue.
What is this : [x] Bug
Where : the component is great for most of usage. The only issue I found is when I use it on an Android app.
How to reproduce it : You need to use the component on a cordova app and run it on Android. The device must have a wedge scanner. ( I suppose this can be emulated with virtual keyboard ?!?! I am not an expert on Android at all )
What happens : When adding debug in the component I noticed that
keypressevent won't give the correcte.whichvalue.e.keyCodedoesn't give anything useful either.Looking on SO, I saw the following post that tells the story better than me.
The solution on this thread doesn't seem to work.. But I was hoping someone could assist me on this issue.
Thanks