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
Hi,
A couple of times I've set up joyride with misconfigured config (eg a bad/mistyped element name). When the user happens to get to the step, joyride just stops working - the curtain is down, but the user has no way of recovering out of the joyride (unless they F5)
Makes sense. While it might be difficult to make it resilient from all sorts of bad config errors.It might make sense to skip for elements that are not present.
Hi,
A couple of times I've set up joyride with misconfigured config (eg a bad/mistyped element name). When the user happens to get to the step, joyride just stops working - the curtain is down, but the user has no way of recovering out of the joyride (unless they F5)
You can see this in the plunkr: http://plnkr.co/edit/Yn7cqL8IpR1VoL1ky65R
I could see this happening on a largish project where element ids change, and the tour is mistakenly not updated.
Can I make a suggestion that for misconfigured configs, that ng-joyride either end the tour, or skip the step?
Thanks,
Steve
The text was updated successfully, but these errors were encountered: