Actualy guided tour are configure to all views but it not necessary and that create a problem of priority for other component
Guided tour need to be activaed via good context
for now in my component i have this
user need to cllic on sall all tours to see the component tours
the good behavior is to display guided tour in his context add home dashboard
Result
in component
in dashboard
in articles
i hope it can be corrected @obuisard
Labels |
Added:
No Code Attached Yet
|
Great happy to help with test
Wonderful, thanks Yannick, the PR will be linked to this issue once ready :-)
There is a potential accessibility issue with doing that. Navigation should always be predictable. In other words if you click on a button on screen one then it should do the same on screen 2
My understanding of that was always that on any given page the button should behave in a reproducible way. I don't understand what is accessible about going to a page and having the current component at the top of the results (as an example) in order to ensure that keyboard users don't have to scroll through long lists of items to find the component they are currently in.
@wilsonge this describes the failure and is almost identical to the request
Labels |
Added:
Feature
|
Status | New | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2023-11-21 18:23:25 |
Closed_By | ⇒ | alikon |
Salut Yannick @micker, I actually am planning to write a PR that adds 'context' to the core tours, so that we can then more easily show/hide tours as you described. We could have all core tours associated with the 'home dashboard', but once in a specific component, like articles, just show the tours linked to articles.