On the last intro step, the skip button is renamed done but still has a 'skip' effect which doesn't call oncomplete.
the next button is also displayed as disabled while the currentStep number is tested against the steps length and doesn't call _nextStep when it's the last one.
Thanks for report, @Floby.
Could you provide an online example on jsFiddle? Or explain it more please.
Hi @Floby I also was having a weird time with the oncomplete method as well, until I setup the introJS() call as a variable. I don't know if you are still having the problems with oncomplete/onexit but try setting the initiated method to a variable name like so:
var myintro = introJs();
myintro.oncomplete(function() { /* some codes */ }
myintro.onexit(function() { /* some other codes */ }
I found another way to do what I needed to do.
Basically I'm in an Ember.js one page app and needed to switch pages when the intro was completed.
Thanks, @jakerocheleau, that worked for me.
I also found out that introJs allows chaining (this solution does not require a local var):
introJs().oncomplete(function() {
/* some codes */
}.start();
Most helpful comment
Hi @Floby I also was having a weird time with the oncomplete method as well, until I setup the introJS() call as a variable. I don't know if you are still having the problems with oncomplete/onexit but try setting the initiated method to a variable name like so: