ng-intro-onbeforechange being called asynchronously about angular-intro.js HOT 3 CLOSED

This is because the DOM isn't always ready (depending on use case) so the safest option is queueing the events up using $timeout. I probably blanket applied it to all the events. If you want you can try removing it then testing it a bit, though without it you may get odd Angular errors if your event handler needs to touch the DOM, so I'm not 100% confident about it.

from angular-intro.js.

I took $timeout out of the call for onbeforechange and for me angular-introjs is now behaving more like introjs does. I think at least for onbeforechange, $timeout is probably not needed.

I'll keep playing with it and I'll probably fork angular-introjs and if it proves successful for us I'll let you know.

from angular-intro.js.

Wouldn't it be possible just to first call the corresponding function and then notify the scope?

if (scope.ngIntroOnbeforechange) {
    intro.onbeforechange(function(targetElement) {
        scope.ngIntroOnbeforechange.call(this, targetElement, scope);
        scope.$digest();
    });
}

Or to be sure that digest isn't already in progress do something like
setTimeout(scope.$digest);

from angular-intro.js.