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
I am trying to use Shepherd in a single-page app, and I just noticed that divs that Shepherd creates to display step content remain in the document when the tour ends. If the page is not refreshed and multiple tours are started the number of those divs grows indefinitely.
Is there any way to clean them up? I mean I can always just remove '.shepherd-step' divs, but why are they kept around?
The text was updated successfully, but these errors were encountered:
Hmm, this seems like a bug. I would at least expect subsequent tours to reuse the existing DOM elements from the previous tour, but it seems to just recreate them. I'll take a look into this and hopefully have it fixed for the next release. Thanks for the catch!
It is the same thing for the style="pointer-events: none;" which gets applied to the target element. If you exit the tour on a button or some other element that has a click action attached to it the element stays inactive.
I am trying to use Shepherd in a single-page app, and I just noticed that divs that Shepherd creates to display step content remain in the document when the tour ends. If the page is not refreshed and multiple tours are started the number of those divs grows indefinitely.
Is there any way to clean them up? I mean I can always just remove '.shepherd-step' divs, but why are they kept around?
The text was updated successfully, but these errors were encountered: