-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question about Detached Tours, Can the tour auto-skip :hidden items #141
Comments
@benmarch thank you, will continue conversation here. I do have a working implementation using a dynamically generated tour based on visible elements that does appear to be working ok. |
Nice! Would you mind sharing some of your code so I can look into incorporating it into the app? (Or at least for my knowledge to help others.) |
Absolutely;
Minor change but also adjusted a bit of the look and feel. We have a quick tour button
For some reason the ui-tour-popups were not being cleaned up, so I on ended do that. Ideally I would be able to use elementId where I am currently doing some more complex jquery locator searches, but I couldn't get that to work so I went w/ this approach This handles missing elements, as well as some changes when in responsive mode |
I am using the exact versions of the following:
I have installed this library via: (NPM, Bower, or downloaded package)
I have observed the following behavior:
This is more a question than an observation. I have tried various tour based utilities and trying to find one that fits our needs.
Is it possible to have a tour step automatically be skipped if display:none is on the item. In jquery this would be :visible as part of the filter to ensure it is actually visible to the user.
As stated in another PR question, we have some elements which only appear under certain resolutions. I'm trying to avoid the view controller needing to be aware of $window width and instead have the tool skip elements which are hidden from the user in the tour.
So far the detached tour seems to be working well, any thoughts on this?
This is how I expected it to behave:
Here is my tour config, and all related step configs:
Additional notes/code:
The text was updated successfully, but these errors were encountered: