-
Notifications
You must be signed in to change notification settings - Fork 829
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
[EuiTour] Support for previous, next and go to step #4831
Comments
I think the full screen example has an example of how to handle this? I'm not super familiar with the component, but that should at least get you what you need?
Does look like we might want to by default add |
Yes, I think adding |
I don't recall any discussion about clickable dots, but I don't see any reason why they can't be clickable. Follow-up question: Would you want to define the |
I can't see any time where it wouldn't be go to nth step. Only thing I could see is that you would want to turn it off for cases where one step can't be completed before another. |
A couple thoughts I've had on this in the past.
|
Those are good points. I agree that the small dots can be hard to click and while I'm guessing a scenario with 10+ steps is unlikely it is true that the current layout could break with so many dots (plus I think it'd be hard for the user to mentally keep track of which steps they've seen). Maybe we could provide two options for If we have to prioritize I'd would say that yes, skipping to the next step should be at top. Like I mentioned, a One option for the |
Based on all this, it seems like the functionality getting very similar to pagination. So what if EuiTour just used EuiPagination in place of the dots, allowing users to use the back/next arrows to go back/forward through the steps and possibly jumping to a specific step if need be. Then you can keep the high priority item of ending the tour where it is (right side of footer) and still prominently allow "Next" or "Okay" buttons in the body of the tour content for specific call-to-actions. |
👋 Hey there. This issue hasn't had any activity for 180 days. We'll automatically close it if that trend continues for another week. If you feel this issue is still valid and needs attention please let us know with a comment. |
Hey all, Security Solution is interested in this as well. We'd like to have some built-in previous/next buttons in the tour steps that would allow the user to navigate between the steps. So far we had to add our custom buttons to the content of every step: elastic/kibana#128405 |
👋 Hey there. This issue hasn't had any activity for 180 days. We'll automatically close it if that trend continues for another week. If you feel this issue is still valid and needs attention please let us know with a comment. |
❌ We're automatically closing this issue due to lack of activity. Please comment if you feel this was done in error. |
I wanted to check with the team and ask if we would consider adding "go to next", "go to previous", "go to nth step" support to EuiTour. Or if this was considered during the development of the component but not implemented for some reason.
We plan to start using EuiTour for Discover and the steps we have are not dependant on each other. In this scenario, being able to skip steps (and go back if needed) could be beneficial for the user. Right now the requirement is to have a
Next
button which I could fit in the step "body" but wanted to see what we think about doing something like this too.The text was updated successfully, but these errors were encountered: