You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 23, 2025. It is now read-only.
Repository navigation
This repository was archived by the owner on Sep 23, 2025. It is now read-only.
First of all, thanks a lot for this module, it is awesome! I just had the problem that sometimes different requests weren't really combined to one loading bar but instead it was going back and forth multiple times. What fixed it for me was simply preventing to set the status to a lower value:
var oldSet = cfpLoadingBar.set;
cfpLoadingBar.set = function (n) {
if (n > cfpLoadingBar.status()) {
oldSet.apply(cfpLoadingBar, arguments);
}
};
Is there any reason not to use this condition?
Cheers,
Jesse
This isn't due to them not being combined into a single loading bar, but rather additional requests went out without responses, so technically, the percentage completed just dropped, and the loading bar visually shows this.
Activity
chieffancypants commentedon Feb 17, 2016
This isn't due to them not being combined into a single loading bar, but rather additional requests went out without responses, so technically, the percentage completed just dropped, and the loading bar visually shows this.
Some initial work here: #150