event-handling

I was wondering two things, in the context of angularJS event handling. How is defined the order in which handlers listening to the same event are triggered? Is it a sign of a bad design if you start wondering about this? After reading documentation on angular $on, $broadcast and $emit as well as native DOM event flow I think I understand in which order event handlers will be trigger in different scopes. The problem is when several handlers listen in the same scope ($rootScope for example) from various places (Controllers vs Services for example). To illustrate the problem I have put together

When discussing the merits of AngularJS, two-way data binding is often touted as a major benefit of Angular over other JS frameworks. Digging deeper , the documentation suggests this process is done through dirty-checking rather than through event-driven measures. At first, it seems that the digest-loop works by having a method fire off in the background at periodic intervals, checking all the $watch es during each cycle. However, reading further, it seems that the digest-loop is actually triggered by rootScope.digest() , which in turn is triggered by $.apply , which is in turn triggered by an

This question already has an answer here: How do JavaScript closures work? 86 answers I'm trying to learn JS and got an issue. I tried many things and googled but all in vain. Following piece of code doesn't work as expected. I should get value of i on click but it always returns 6. I'm pulling my hair out., please help. for (var i = 1; i < 6; i++) { console.log(i); $("#div" + i).click( function() { alert(i); } ); } jsfiddle Working DEMO This is a classic JavaScript closure problem. Reference to the i object is being stored in the click handler closure, rather than the actual value of i .