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
When mixing steps between those that require user interaction and those that only highlight items it's useful to turn on and of the next button for every step independently. As much as this works for the previous button, it doesn't for the 'next'.
The only way to bring back the next button after it was hidden once is to use the event_type: next. It's not a big issue, but on the other hand it prevents us from also accepting 'click' as an alternative condition to move to the next step, which in some cases is still convenient to have.
This behavior is rather clear from the code:
//here, unless specifically set to true 'next' is hidden, but if it was hidden already, regardless the value, there is no logic to show it
if (step_data.showNext !== true) {
$body.enjoyhint("hide_next");
}
$body.enjoyhint("hide_prev");
if(current_step !== 0) {
$body.enjoyhint("show_prev");
}
if (step_data.showPrev == false) {
$body.enjoyhint("hide_prev");
}
if (step_data.showSkip == false) {
$body.enjoyhint("hide_skip");
} else {
$body.enjoyhint("show_skip");
}
I believe that forcing showNext: true should still allow to show the next button regardless the event type.
The text was updated successfully, but these errors were encountered:
When mixing steps between those that require user interaction and those that only highlight items it's useful to turn on and of the next button for every step independently. As much as this works for the previous button, it doesn't for the 'next'.
The only way to bring back the next button after it was hidden once is to use the
event_type: next
. It's not a big issue, but on the other hand it prevents us from also accepting 'click' as an alternative condition to move to the next step, which in some cases is still convenient to have.This behavior is rather clear from the code:
I believe that forcing
showNext: true
should still allow to show the next button regardless the event type.The text was updated successfully, but these errors were encountered: