Hi team,
\n
Can anyone help me with the below notification and if Articulate will change/have an impact in anyway.
\n
Summary
\n
Google has announced a browser change that may prevent your courseware from correctly bookmarking user progress and recording completion when a user navigates away from a course. The unload event will be gradually deprecated starting in Q3 2024 and ending with 100% of sites by Q1 2025. Your courseware may rely on the browser unload event for course communication. Microsoft Edge is built on the same codebase as Chrome and may also be affected. The unload event deprecation will impact a variety of course authoring tools and learning content standards. Choices such as the device used to launch learning (desktop/mobile), or the launch method (new window/inline) may also impact whether issues are present.
\n
The following are common scenarios where the unload event deprecation may cause issues:
\n
\n- Leaving a course using the Item or My Learning breadcrumb
\n- Leaving a course using the SCORM 2004 navigational buttons
\n- Leaving a course using the browser exit button
\n- Clicking the “Verify Course Completion” button
\n
\n
To align with these changes, Learning ended support for unload browser events in 2H 2023 in our application. However, this will not resolve issues with content that uses the unload event.
\n
Next Steps/Customer Action Items:
\n
As this change is with how content handles standards in place from browsers, this is not a defect with the SAP SuccessFactors Learning Management System. If you partner with a content vendor, check with them on how they’re preparing for the unload event deprecation. If you create your own content, check with your content authoring tool on how they’re preparing for the unload event deprecation. Also, review the options provided by Google here for identifying and replacing usage of the unload event. More info is linked below. Considering these changes, the Learning team is currently exploring if changes can be made to mitigate some of the issues we are seeing after testing the most common authoring tools.
\n
\n
Thanks Chris
Hi team,
\n
Can anyone help me with the below notification and if Articulate will change/have an impact in anyway.
\n
Summary
\n
Google has announced a browser change that may prevent your courseware from correctly bookmarking user progress and recording completion when a user navigates away from a course. The unload event will be gradually deprecated starting in Q3 2024 and ending with 100% of sites by Q1 2025. Your courseware may rely on the browser unload event for course communication. Microsoft Edge is built on the same codebase as Chrome and may also be affected. The unload event deprecation will impact a variety of course authoring tools and learning content standards. Choices such as the device used to launch learning (desktop/mobile), or the launch method (new window/inline) may also impact whether issues are present.
\n
The following are common scenarios where the unload event deprecation may cause issues:
\n
\n- Leaving a course using the Item or My Learning breadcrumb
\n- Leaving a course using the SCORM 2004 navigational buttons
\n- Leaving a course using the browser exit button
\n- Clicking the “Verify Course Completion” button
\n
\n
To align with these changes, Learning ended support for unload browser events in 2H 2023 in our application. However, this will not resolve issues with content that uses the unload event.
\n
Next Steps/Customer Action Items:
\n
As this change is with how content handles standards in place from browsers, this is not a defect with the SAP SuccessFactors Learning Management System. If you partner with a content vendor, check with them on how they’re preparing for the unload event deprecation. If you create your own content, check with your content authoring tool on how they’re preparing for the unload event deprecation. Also, review the options provided by Google here for identifying and replacing usage of the unload event. More info is linked below. Considering these changes, the Learning team is currently exploring if changes can be made to mitigate some of the issues we are seeing after testing the most common authoring tools.
\n
\n
Thanks Chris
more infos
\n
https://community.articulate.com/discussions/articulate-storyline/does-deprecating-the-unload-event-in-chrome-will-impact-our-scorm-trainings-build-with-storyline-or-rise
\n
=> current versions of storyline and rise 360 do not appear to be affected
\n
i have check all storyline web player from 3.60 (January 2022) to the current version
\n
unload event is not used
\n
I have also checked 2 older versions
\n
\n- 3.19 (August 2018)
\n- 3.25 (February 2019)
\n
\n
if have found in app.js e.g.
\n
e.ActiveXObject && b(e).on(\"unload\", function() {\n
This means that Articulate fixed the potential problem in Storyline 360 between February 2019 and January 2022.
\n
@articulate: have a look at your version control program (Perforce, Mercurial, Git ???) - you should be able to find out very quickly from which version unload was no longer used
\n
@articulate: you have to test whether for in the past published courses cause problems with “unload” and then publish the info here in the forum
