Chrome 80 update

Hi

I have just been notified by our LMS provider (Cornerstone) that changes will be made in Chrome 80, due for launch in Feb 2020, that will significantly affect the window close behavior and as a result course tracking.

Whilst Cornerstone are issuing an update for their SCORM player, do Articulate anticipate or have planned any updates that may be required for published Storlyline 360 and Rise courses?

Regards

Jeremy

38 Replies
Alyssa Gomez

Hi, Sharon! I have an update for you about Rise 360 courses published to AICC or TinCan. 

We added support for Google Chrome 80, which no longer allows synchronous XHR when a web page is closed. This update ensures your AICC courses always communicate a final status to an LMS. You'll need to re-export your AICC and xAPI courses so that they continue to work with Chrome 80.

Ren Gomez

Hi SibaPrasad and Chris,

I'm sorry you're running into issues with reporting completion for Rise 360 courses using Chrome 83! This discussion should help provide more insight around the issue until we get it resolved.

Crystal Horn

Hi everyone. Quick update if you're experiencing issues with Chrome or Edge allowing learner progress or completion to be retained when a course is closed:

Chrome has deprecated a technology that was used by many LMSs to allow a course to communicate back to the LMS when the course window is closed. If your LMS hasn't upgraded their system, or if you're using an older version of your LMS that doesn't include an update to address this change, the course cannot communicate progress or completion properly. This causes learners to start over from the beginning instead of resuming a course or recording completion after they close the browser window.

Please reach out to your LMS and find out if they have released an update to address the Chrome changes. If you need support from us with the technical details, please let us know by starting a case with us here.

Katie Riggio

Hi Gerard,

Thanks for sharing what you're experiencing! The discussion that Ren shared is a good place to start:

We're having a look at this behavior, and we've seen that making this adjustment in Chrome 83 has helped in some LMS environments:

1. Open Chrome browser
2. Go to chrome://flags/#allow-sync-xhr-in-page-dismissal
3. Change the drop-down selection from Default or Disabled to Enabled

We'll let you know if we are able to make changes to Rise 360 output that would help.

Let us know if any more questions pop up. We're also happy to work directly with you in a case!

Christian Gainsbrugh

Hello Articulate Team! 
I work over at LearningCart LMS and a LOT of our customers use Articulate products. Chrome 80 has presented a lot of challenges but I think ultimately the solution in addressing these issues needs to be a collaboration between Authoring Tools and LMS providers. 

The issues we have seen our customers run into have to do with content attempting to save progress when a user exits their browser.  The easy work around to this is for authoring tools to ensure their SCORM modules are calling LMSCommit() when progress needs to be saved.  That is a standard SCORM call, can be called by the content whenever needed, and would completely circumvent the Chrome 80 issue because it can be called on each page/slide load or when completion is triggered. 

On our end we have implemented the appropriate updates to handle asynchronously saving data when a course exits - HOWEVER in some cases that is not able to completely address the issue. Chrome does impose limits on the length of data that can be saved when the browser window exits - both for async http calls as well as the sendbeacon work around that a lot of LMS's have implemented.  For many courses the length of the data being saved isn't an issue, but we have seen if you have a SCORM 2004 course with a quiz, where it is saving question responses/interactions then your saved data can VERY easily exceed 64kb. Keep in mind the 64kb limit in SCORM 2004 is just for the value of data for a specific element - like suspend data - Its NOT intended to be a limit on the size of ALL CMI data.   Again the simple work around from an authoring tool perspective would be to ensure that all data is being saved (via LMSComitt()) as updated instead of when a user closes their browser window.   From what we have seen, Articulate is MUCH better at more frequently saving data than many other Authoring Tools but it doesn't seem to quite be 100%.   Just wanted to pass these thoughts in the hopes that perhaps your dev team could review them and perhaps factor them into a future update.





Lauren Connelly

Hi Christian!

Thanks for sharing those details! Data is sent after every slide, and we compress that data, so with most courses, you shouldn't run into the 64kb limit unless it's an extensive course. 

Your clients can reach out to our Support Engineers if they run into any snags with their files! You can share this link, which will connect them with one of our Support Engineers.