chips: SPACE separator does not work with virtual keyboards on Android
#9.237 aberto em 4 de jan. de 2018
Métricas do repositório
- Stars
- (24.044 stars)
- Métricas de merge de PR
- (Mesclagem média 3d 12h) (98 fundiu PRs em 30d)
Description
Bug, feature request, or proposal:
Bug
What is the expected behavior?
Separate chips on space when SPACE is set in MatChipInput.matChipInputSeparatorKeyCodes
What is the current behavior?
On Android devices it does not. (I personally tried Nesus X5 and pixel xl v1)
What are the steps to reproduce?
https://stackblitz.com/edit/chipinput "android friendly chip input" uses keyup and looks at the last char of the input's value, to get around Android's "bad" keyboard event w/o keys and indistinguishable keycode 229.
What is the use-case or motivation for changing an existing behavior?
To be able to use MatChipInput on Android.
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
All but on Android devices
Is there anything else we should know?
Android produces keycode 229 on space and other special characters. Related to https://stackoverflow.com/questions/36753548/keycode-on-android-is-always-229/42552368