Skip to content
This repository was archived by the owner on Apr 12, 2024. It is now read-only.
This repository was archived by the owner on Apr 12, 2024. It is now read-only.

$evalAsync does not always get executed in the current $digest cycle (1.0.0rc8) #947

Closed
@tbosch

Description

@tbosch

Hi,
when I have a scope that contains a single $watch, which uses $evalAsync, then the $evalAsync does not get executed until the next $digest cycle, but not in the current $digest cycle.

Here is a jsfiddle to show the problem: http://jsfiddle.net/GGbzx/1/

When you type a character into the textbox, the $watch fires and logs the current value using $evalAsync to the console.
However, in this case, the value that is logged is not the current value of the input field, but the last value (e.g. type in "aaa", then the log only shows "aa".

Tobias

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions