Is there a way to stop a storyline module from playing when a viewer opens a new browser window? So that when they come back, they can resume where training left off? We're having issues with employees clicking out to check email, etc. Thanks for any insights.
Thanks for reaching out! In the most recent update of Storyline 360, audio and animation in the HTML5 output will pause if the learner opens a new browser tab or minimizes the browser window. However, audio and animation will continue playing if the learner opens a new browser window. Our team is looking into this to determine what is expected behavior, and we'll let you know if we get an update.
In the meantime, you may want to check out this Javascript workaround another community member shared here.
Thanks for the insights and link, I'll check it out.
In the meantime, a couple of questions. 1) does this only work when publishing in HTML 5, or does it work when publishing in HTML 5 w/ Flash fallback (which is how we publish). 2) We use a read only-seek bar - do you know if this pauses along with the audio and animation?
If you publish HTML5 only or HTML5/Flash, then you'll be directed to the HTML5 output, and the audio and animation will pause if the learner opens a new browser tab or minimizes the browser window.
This happens no matter if you're using a read-only seekbar or a draggable seekbar.
When I send the learner out, I send them first to a layer (which stops the timeline) that instructs them that they will go to a different site, and that they can close that new tab or window, or maintain it open. When they are ready to continue, they should click a Resume or Continue button on the layer, which closes and resumes the timeline.
Thanks for your patience while we took a look at this! Our team implemented an additional fix in the latest update to help with the continued issue where an animation continues to play in HTML5 when navigating away from the browser tab.
Just launch the Articulate 360 desktop app on your computer and click the Update button for each application (in this case Storyline). Details here.
8 Replies
Hi there Dave,
Thanks for reaching out! In the most recent update of Storyline 360, audio and animation in the HTML5 output will pause if the learner opens a new browser tab or minimizes the browser window. However, audio and animation will continue playing if the learner opens a new browser window. Our team is looking into this to determine what is expected behavior, and we'll let you know if we get an update.
In the meantime, you may want to check out this Javascript workaround another community member shared here.
Hi Alyssa,
Thanks for the insights and link, I'll check it out.
In the meantime, a couple of questions. 1) does this only work when publishing in HTML 5, or does it work when publishing in HTML 5 w/ Flash fallback (which is how we publish). 2) We use a read only-seek bar - do you know if this pauses along with the audio and animation?
Again, thanks,
Dave
Great questions, Dave!
Let me know if you think of anything else!
Thanks, Alyssa, for the prompt response. I appreciate it and look forward to updating Storyline 360 to test this out. Will keep you posted :)
Sounds like a plan, Dave. Thanks!
Dave,
When I send the learner out, I send them first to a layer (which stops the timeline) that instructs them that they will go to a different site, and that they can close that new tab or window, or maintain it open. When they are ready to continue, they should click a Resume or Continue button on the layer, which closes and resumes the timeline.
Thanks, Walt! Sorry for the late response, I was away from Storyline for a bit! I'll check it out.
Hi all,
Thanks for your patience while we took a look at this! Our team implemented an additional fix in the latest update to help with the continued issue where an animation continues to play in HTML5 when navigating away from the browser tab.
Just launch the Articulate 360 desktop app on your computer and click the Update button for each application (in this case Storyline). Details here.
This discussion is closed. You can start a new discussion or contact Articulate Support.