Last modified: 2014-06-09 22:16:03 UTC
For example, rather than making them click the X or even an Okay button wired to action: 'end', just end it automatically on post-edit. This can fit into the proceedTo idea we've been brainstorming. E.g. that can return 'endTour' to end the tour completely. Not having this makes it more likely for an unwanted (or past its useful life) tour to linger until the cookie expires or the user explicitly chooses an end action. For example, this can be reproduced by making an edit with the 'firstedit' tour, then previewing any page (since we also chose not to use stickToFirstPage for this tour)
We may also want to end some tours automatically when the last step is displayed. It would not hide the actual guider without a user action, but it would never show again.
This really makes sense in light of recent data collected via Schema:GuidedTour, where many users viewed certain steps (1-4) multiple times unnecessarily. Tl;DR: users will behave in unexpected ways. We should save them from themselves.
At least part of this will be handled by the new non-linear tour work. In addition to skipping to a normal step, there will be special skip actions, initially 'hide' and 'end. So it will be possible to end the tour at any time, by skipping.
For example, a tour writer could specify that any postEdit mw.hook event triggers ending the tour.
Forgot to tag this, but non-linear tours fixed this. See https://git.wikimedia.org/blob/mediawiki%2Fextensions%2FGuidedTour.git/ba4306798ecc72ef94da61d061e44d19c019f32f/modules%2Fext.guidedTour.lib%2Fext.guidedTour.lib.TransitionAction.js#L15
