Progress bar does not go away after calling complete()

[sthomp]

Progress bar does not go away after calling complete()

[oblador]

I've noticed this as well, looks like an issue with the interval not getting cleared properly to me. I'd suggest migrating to $timeout instead of setInterval to make it more angulary.

[Grigorius]

I have changed setInterval to $timeout and it appears to have solved this problem for me.

http://plnkr.co/edit/XG9KIqje9eD13ms3l81N

[oblador]

Haven't tried it, but it looks like you broke the faux progress functionality (which is the whole point of this directive). You will need to set the $timeout again and again if you want to mimic setInterval functionality.

[Grigorius]

the faux progress isn't broken - the loading is too fast ... (I think)

[oblador]

It is, comment out ngProgress.complete(); and nothing happens.

[Grigorius]

Ups, yes you are correct!

[voronianski]

@oblador @Grigorius @sthomp I developed an alternative angular.js provider (due to a lot of issues in this one), it's called ngProgressLite - http://labs.voronianski.com/ngprogress-lite.js/

It's small and has same API as original jquery plugin. You can check it out and maybe it will suit you.

[Grigorius]

I'm currently using this: http://ricostacruz.com/nprogress/

[sthomp]

Thanks, will take a look

[voronianski]

@Grigorius yeah, ngProgressLite is a port of it to angular.js with the same API, it's not a good practice to be dependant on jquery in angular app.

[gsabater]

Looks like due to the lack of updates and / or feedback, and several problems with this issue, i'm movin to ngprogress-lite too. Lets see how it works.

[voronianski]

@bondaestudi thanks! spread a word about it to get users that are coping with troubles here to swtich to more stable solution

[avances123]

this bug happens to me also, @victorbjelkholm is not developing this anymore?

[dasois]

@avances123 no he currently does not have the time.
I've taken over the development of this basically and planning to get this straight. Bugs/wishes/code are very welcome!

[dasois]

@sthomp @oblador @avances123 @Grigorius does this bug still affect you with the current version? If true, than please clarify.