I'm submitting a ...
[x] bug report
[ ] feature request
[ ] support request
Current behavior
On mobile, ngModelChange is only triggered on completion of typing a word (e.g. by hitting space or enter), rather than on every character input.
Expected behavior
As in 2.x, ngModel should emit every time a character is typed.
Minimal reproduction of the problem with instructions
http://embed.plnkr.co/bXrMnRI9GyRbzR9r19sZ
On desktop, this logs the text of the textarea each time a character is typed, as expected.
On mobile, the change event is only triggered after completing a word, such that typing a sequence of non-whitespace characters or swyping a word won't register any changes.
What is the motivation / use case for changing the behavior?
In the case of @cyph, this bug is causing the following incorrect behaviour in our development branch:
(In the first screen, the message box hadn't transitioned to show the send button as was expected. In the third screen, the last word of the intended message wasn't included because ngModel hadn't updated the message value.)
Please tell us about your environment:
-
Angular version: 4.0.0-rc.2
(Edit: also reproduced with 4.0.0-rc.3)
-
Browser: Mobile Chrome 56 and Mobile Firefox 52 on Android 6.x
-
Language: TypeScript 2.2.1
I'm submitting a ...
Current behavior
On mobile,
ngModelChangeis only triggered on completion of typing a word (e.g. by hitting space or enter), rather than on every character input.Expected behavior
As in 2.x,
ngModelshould emit every time a character is typed.Minimal reproduction of the problem with instructions
http://embed.plnkr.co/bXrMnRI9GyRbzR9r19sZ
On desktop, this logs the text of the textarea each time a character is typed, as expected.
On mobile, the change event is only triggered after completing a word, such that typing a sequence of non-whitespace characters or swyping a word won't register any changes.
What is the motivation / use case for changing the behavior?
In the case of @cyph, this bug is causing the following incorrect behaviour in our development branch:
(In the first screen, the message box hadn't transitioned to show the send button as was expected. In the third screen, the last word of the intended message wasn't included because
ngModelhadn't updated the message value.)Please tell us about your environment:
Angular version: 4.0.0-rc.2
(Edit: also reproduced with 4.0.0-rc.3)
Browser: Mobile Chrome 56 and Mobile Firefox 52 on Android 6.x
Language: TypeScript 2.2.1