@carlosadrian wrote:
Let's suppose we have this ion-input:
<ion-input type="number" [(ngModel)]="quantity" (change)="doSomething(quantity)"></ion-input>
The method doSomething() needs the NEW entered quantity to, obviously, do something
![]()
The problem here is when I use the browser arrows for type number (up and down little arrows for increment and decrement the value), because they do not trigger the (change) event. They do trigger the (input) event, but input event gets the old quantity, not the new one entered.
Is it the expected behaviour or is it a bug?
Thank you
Posts: 1
Participants: 1