The example for the issue described here can be checked on CodePen.

Let's assume you have the following setup:

• An input field with ngModel on it, having ng-model-options="{updateOn: 'blur'}"
• A button with ngClick on it, where the handler function using the value of the model from scope

Executing the following steps has different results on mouse and on touch devices:

• Edit the input value
• Click on the button directly (without clicking anywhere else first)

With mouse based input the ngClick handler can access the current input value on scope, and it is the same value that you can see in the input field.

On touch devices however, when the ngClick handler is executed the value is not updated yet (see the CodePen example with Chrome DevTools device emulation to see it happening).