|
|
|
|
|
by lucisferre
4029 days ago
|
|
It's not the same thing, as the author points out since using `$timeout` in the example without an isolate scope was the source of the original problem. Instead he's suggesting you use $timeout without it's default behaviour (something that's possible now through the false argument or by calling setTimeout directly). This is absolutely a leaky abstraction, and whether or not it's necessary sometimes when using Angular, it should still bother you. |
|