Fixes bug on Android/Chrome because Android does not sends the correct keyCode

[gnarvaja]

Manually detects comma from the input text.

[dprea]

@gnarvaja The travis report shows you only need to change '==' to '===' on line 416 to pass the tests.

I have tested this code in Chrome Desktop and Android Chrome and it does seem to fix the problem with comma.

[coveralls]

Coverage decreased (-0.4%) to 99.336% when pulling 46f609b on lambdasistemas:master into af9feb7 on mbenford:master.

[SammyIsra]

Was the problem that it would not detect when a user on Android or Chrome pressed the comma key? If that is the case, I am experiencing something similar.

[coveralls]

Coverage decreased (-0.4%) to 99.336% when pulling a467d2c on lambdasistemas:master into af9feb7 on mbenford:master.

[calebfaruki]

This getting merged anytime soon?

[mikesnare]

Just wanted to note that this is not working for me. Not sure how it works for anyone. First, it only handles the comma case but the component supports space and enter as well. Second, and more importantly, because this runs during the keydown event, the input has not been updated with the key that was pressed. I.e. if the value of the input field is a@b.com and you type the comma, the comma is not part of the value during the event. The value is still a@b.com because the keydown happens before the value is updated. You'd need to type the comma again, and then it would work.