Forum Discussion
Google Unload Event Depreciation
Hi Articulate Team
I've just been sent an email from our IT department about Google depreciating the Unload Event (?), which according to them, may impact on learners course completions. Below is ...
Hi is there a public answer Articulate can provide for those that haven't filled out a support ticket?
Hi Irene,
Sharing with you what our support team shared with Hannah!
"You’re right about the unload event and its deprecation in Chrome. To clarify, while the Rustici driver we use to communicate with LMSs still includes that unload event, both Storyline and Rise 360 don’t rely on it for essential functionality. We’ve already moved away from depending on unload events, recognizing they’re not considered good practice.
As you pointed out, Rise doesn’t depend on unload events, making it a great option for building more browser-friendly, future-proof courses. You can recreate or adapt your courses in Rise 360, which offers a modern, responsive design framework.
Alternatively, you can use Storyline 360 for highly customized interactivity and Rise 360 for a streamlined course-building experience. By embedding Storyline blocks into your Rise courses, you can maintain the interactivity and complexity of your Storyline content within the flexible framework of Rise 360.
This article explains how to embed Storyline 360 courses in Rise 360 and answers common questions about how learners interact with them."
Feel free to open a case with our support team here if you have further questions or need clarification!
I'm going to submit a ticket, but wanted to get a little further clarity on the "Rustici driver we use to communicate with LMSs still includes that unload event". That is the issue many of us are worried about, as we tend to export Storyline packages in SCORM format to upload to an LMS. If the Rustici code is still using that unload event, will the storyline package fail to communicate with the LMS?
