Numpad decimal separator does not work on IE11 with a keyboard whose numpad decimal key outputs a comma

Current behavior

The numpad decimal separator on german keyboards produces a , (comma). When setting decimalCharacter to , (comma) and digitGroupSeparator to . (dot), the numpad decimal separator on a german keyboard is not recognized as , (comma) in IE11 (although it produces a , (comma) event.char) and thus not allowed as input. It works flawless in current versions of Firefox and Chrome.

It also works when setting decimalCharacterAlternative to . (dot), however, that should not be necessary as per documentation.

Expected behavior

The numpad decimal separator should be accepted as , (comma).

Steps to reproduce the problem

1. Use autoNumeric version 4.4.0
2. In the browser Internet Explorer version 11
3. On the Windows operating system
4. Then instantiate the autoNumeric object with the following options:

new AutoNumeric(domElement, {digitGroupSeparator: '.', decimalCharacter: ','});

1. Numad decimal character on german keyboard can not be entered.

Link to live example (ie. Codepen)

The issue is reproducible on the autonumeric home page (http://autonumeric.org/) when scrolling down to the example and selecting the third example provided (the separate examples page can not be used in IE11 either, but that’s a different problem)

[AlexandreBonneau]

Using your jsfiddle, when I use my numpad . key, I get [NumpadDecimal Delete #46 undefined]. This is under Firefox 67.0b13, with the us_intl keyboard layout (and a Dvorak keyboard). Under Chromium 73, I get [NumpadDecimal #46 undefined].

I checked under Firefox, Chromium, Firefox for android and Chrome for android, and will take your words for Safari and Edge, and indeed event.char is undefined for those main browsers.

I’ll merge @McNetic PR, thank you both for your researches!

I’ll publish the updated version as soon as I manage to fix all the unit and e2e tests that became red after I updated the dependencies :x

[sbusch]

FYI, a new version 4.5.6 has been released, which includes this fix. Thanks @AlexandreBonneau !

I tested the new release, and can confirm that the fix works for IE 11 and there’s no regression (tested with current version of Firefox)