You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is the use-case or motivation for changing an existing behavior?
Event shouldn't fire twice it is extra and bad performance wise
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
5.2.2
Is there anything else we should know?
Open console inside developer tools and look at console when changing value of Age inside my StackBlitz example. You can see that when you change value of age event is fired once and then when you move your focus on other component it fires second same event again.
The text was updated successfully, but these errors were encountered:
It seems that angular (not material) is just forwarding the standard html behavior: emitting a change event on keydown and when the element loses focus.
Bug, feature request, or proposal:
Bug
What is the expected behavior?
matInput with type="number" shouldn't fire valueChanges event twice, when inside ReactiveForm
What is the current behavior?
matInput with type="number" fires valueChanges event twice, when inside ReactiveForm
What are the steps to reproduce?
https://stackblitz.com/edit/type-number-input-2-value-changes-fired
What is the use-case or motivation for changing an existing behavior?
Event shouldn't fire twice it is extra and bad performance wise
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
5.2.2
Is there anything else we should know?
Open console inside developer tools and look at console when changing value of Age inside my StackBlitz example. You can see that when you change value of age event is fired once and then when you move your focus on other component it fires second same event again.
The text was updated successfully, but these errors were encountered: