"Exit Course" trigger on SL3/HTML5
Feb 15, 2018
I know the "Exit Course" trigger in SL3 doesn't close the course window when running in HTML5 on a number of key browsers. (It also has stopped working for me in Safari 11.0.3.) But does the trigger do anything else?
I just discovered that a JavaScript trigger of 'parent.postMessage("closeWindow", "*");' DOES close the window on Chrome and Safari in our LMS setup (haven't tested Firefox yet) ... but I want to make sure I'm not missing out on any necessary housekeeping that "Exit Course" was doing. (And if I put the JavaScript after "Exit Course," it never runs.)
8 Replies
Hello Eric,
It may be beneficial to take a step back and understand why the Exit Course trigger may not be working and perhaps try the suggestions in the article.
If that does not work well for you, it sounds like you have a great solution as long as this marks your course as completed within your LMS as well.
Thanks — yes, I tried all those. We're looking for a solution that works in all browsers, even those where SL's native "Exit Course" trigger is documented as not working in HTML5. (https://articulate.com/support/article/Storyline-360-and-Storyline-3-Exit-Course-Trigger-Doesn-t-Work-in-All-Browsers) Courses we develop in Captivate exit cleanly using native triggers, so we're trying to duplicate that end-user experience in SL courses.
I just wanted to make sure we've accounted for any other functions or calls that "Exit Course" would do beyond closing the window... sounds like I'm not missing anything important in that trigger.
Hi Eric,
Did you find a solution to the closing window issue? Thanks.
Hi, Kevin! We did ... sort of. Turns out our Web-development team had put a JavaScript on the page where our courses are loaded via an iFrame, which "listens" for a window-close JS call coming from the courseware.
So, I've started doing three things when the user clicks one of our "Exit" buttons: Execute JavaScript "parent.postMessage("closeWindow", "*");", then use SL's native "Exit Course" trigger (in case the JS fails), and then as an ultimate fall-back, lightbox a slide that tells the learner they can safely close the browser tab/window manually. Heavy-handed, perhaps, but I think we've caught 99% of possible scenarios for our users...
Hi Eric. recently we've had problems with our storyline 360 content working in chrome and in the SuccessFactors mobile app. after a recent upgrade to our LMS icontent server, some of the problems were fixed; mostly navigation and working in Chrome. However, the exit course button trigger works in the course when launched in chrome/IE browsers but does not work the same in the mobile app of SuccessFactors learning. I tried both your JStriggr and still used the exit course trigger but I also used "window.close();" as a trigger, and kept the exit course trigger (after the js trigger). Neither republish would exit the course in the mobile app and both continued to work in the Chrome and IE browsers. Is there anything else you can think of to try? I appreciate your contribution here. We are still working with SAP.
Sorry ... what I did was on the outer edges of my knowledge. Our Web team had put in a script on their side that was looking for our closeWindow call in the courseware, so it's a solution specific to our in-house setup.
I do still have that ultimate fall-back: a lightbox slide that instructs learners that they can close the tab/window themselves. It's the last trigger, so it only appears if all the other steps fail.
Thank you and I appreciate your thoughts. Through all my searches last night and attempts to close the window with JS triggers, I kept seeing the term "lightbox" being used, so I had to go look it up and watch a video of one being created (by Articulate). I had no idea what that was. so I learned about it by watching Kevin Durant lightbox video. :-) my son appreciated it. he said, "mom, i didn't know you were this cool". lol
Just saw this awesome comment about your son. My daughter has not figured this out yet!
This post was removed by the author
This discussion is closed. You can start a new discussion or contact Articulate Support.