Skip to content
This repository has been archived by the owner on Feb 26, 2024. It is now read-only.

Keep the native behaviour of setTimeout, i.e. returning a numerical ID of the timeout instead of a task #361

Closed
hmdhk opened this issue Jun 13, 2016 · 3 comments
Closed

Keep the native behaviour of setTimeout, i.e. returning a numerical ID of the timeout instead of a task #361

hmdhk opened this issue Jun 13, 2016 · 3 comments

Comments

@hmdhk
Copy link
Contributor

hmdhk commented Jun 13, 2016

No description provided.

@hmdhk
Copy link
Contributor Author

hmdhk commented Jun 13, 2016 •
edited
Loading

#341 #314 #360

@hmdhk hmdhk changed the title Keep the native behaviour of setTimeout, i.e. returning a numerical ID of the timeout Keep the native behaviour of setTimeout, i.e. returning a numerical ID of the timeout instead of a task Jun 13, 2016
@chuanqisun
Copy link

chuanqisun commented Jun 15, 2016 •
edited
Loading

I encountered the same issue with Angular 1.5.3 + 2.0.0 rc.1 upgradeAdapter. I'm building with node 5.11.1 and npm 3.8.6.

As a result, I am seeing "digest already in progress error", and the $timeout.cancel() no longer works.

image

@vicb
Copy link
Contributor

vicb commented Jun 15, 2016

Duplicate of #314

@vicb vicb closed this as completed Jun 15, 2016
@chuanqisun chuanqisun mentioned this issue Jun 23, 2016
Closed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@vicb @chuanqisun @hmdhk