Siddique Hameed

Do you still have `timer` injected as a service to your controller?

Timer module don't expose any service at this point. Can you try removing it?

agreed.. been wanting to refactor/remove this dependency. But, haven't got a chance

Can you create a plunkr for this issue? It's just using browser's `setTimeout` & I am not sure if there is anything else we can do to avoid this.

@delphiactual - yearUnit comes from `timeUnits` - https://github.com/siddii/angular-timer/blob/master/app/js/_timer.js#L236 which is from `i18nService` - https://github.com/siddii/angular-timer/blob/master/app/js/_timer.js#L175 Can you see if `secondUnit` or `minuteUnit` is working? If not, then something might be broken...

The version used for HumanizeDuration in the website is https://github.com/siddii/angular-timer/blob/master/bower_components/humanize-duration/bower.json#L14 Worth the shot

Yes, thats definitely possible. But, you probably want to build a new directive based off of this one.

I think you might be running into a issue of multiple `timer` on the same page. Possibly scope collisions? Can you try it without `ng-if`?

Interesting.. so, do you want to see countdown like -10 minutes: -5 seconds etc. ? Obviously, thats not a general countdown behavior. May be some rolling countdown or something.. Curious......

You cannot set the timer's start time from an asynchronous call after directive compilation (page load). You need to re-compile the directive after the async response & attach it to...