Chrome 78 release on 22 October

Oct 17, 2019

We received an email from a client asking about the new Chrome update.  Will Articulate products work with this version of Chrome?

We want to alert you to an important browser update which may impact your content. The upcoming release of the Google Chrome browser (Release 78) scheduled for release on 22 October contains a significant change which may impact course tracking in the OpenSesame player and LMS platforms.

Because of the potential impact on our mutual customers, we ask that you reply to this email by 9 October and notify us what your team is doing to prepare for this change. We plan to communicate to customers later this week and anticipate questions about publisher actions in response to the Chrome release.
Chrome 78 release on 22 October
The new Chrome release scheduled to come out on 22 October will disallow posts to external URLs to happen when the browser is closing or navigating away. As a result, courses which are authored to be marked complete on-exit or posting data to an external URL (most likely to be AICC in the browser or remote hosted SCORM) may no longer work. As a result, learners’ progression through courses might not be saved. After this release, learning management systems, particularly those recording completion on exit, may fail to receive completions under Chrome.

More information, including Google’s recommendations for a fix can be found here. Please see the section “Disallow sync XHR in page dismissal”. The quickest change is likely replacing your POST or GET requests with a FETCH having the keepAlive=true set. You can test using Chrome 78 by downloading it here.


Thanks, Steve.


37 Replies
Leslie McKerchie

Hi Steve,

Looks like Brian has nailed it.

Google plans to end support for synchronous XHR in Chrome 80 when it's released in January 2020. You can learn more about this change here:

The good news is that SCORM and Tin Can API (xAPI) courses are unaffected by this browser change.

However, AICC courses could be impacted. Learner interactions that happen in the final few seconds before they close the browser tab might not get communicated to the LMS.

We're working on a solution for this issue now. I'll be sure to let you know as soon as we have steps for updating your AICC courses so they're fully compatible with Chrome 80.

I'd also recommend checking with your LMS admin or provider to see if your LMS uses synchronous XHR so they can update your system before Chrome 80 is released.

Craig Childs

I'm a bit surprised (but relieved, if true) to hear that SCORM courses won't be affected as Mike Rustici over at indicates that Google ending support for synchronous XHR in Chromium 80 will affect "almost everyone" using SCORM. 

"The following conditions must be met for this issue to come into play:

  1. The learner must be using Google Chrome 78 (or above). [Pushed back to Chrome 80]
  2. The course must be a SCORM course.
  3. The learner must exit the course by closing, or navigating away from, the window/frame that contains Engine's SCORM player page."

As I understand it this means that if a user exits a course by closing the course window (rather than clicking an exit button) then the final communication to the LMS will fail.   He says the issue is more likely to affect courses launched within an iframe.

The post is primarily concerned with changes that will need to be made to the Rustici SCORM Cloud engine, but I believe Articulate uses Rustici code in their SCORM solution, so it would be great to have confirmation that this doesn't apply here.

Lauren Connelly

Not to worry, Craig! We've been working closely with Rustici on this issue since the moment we heard about it.

The problem primarily impacts SCORM Engine, which is a product used by LMS vendors. Articulate also partners with Rustici on their SCORM Driver product, but this tool isn't as impacted. The exception is AICC content, and we'll be working on a fix for AICC soon. We're very confident that content published from Articulate authoring tools for SCORM and xAPI is not impacted, so we've got you covered!

Logan Stahler

We received documentation from our LMS provider stating something similar. Question - as long as the trigger to complete the course (either submitting a score or setting completion) happens before the final slide and via its own button (not an exit button) or at the start of a timeline, there shouldn't be an issue, right? 

Mara Merchant
Christina Clark

So I have a SCORM package that no longer records a score nor a completion status in Docebo. It worked perfectly when we last used it in July. It worked for a couple users who completed it at the beginning of last week (4th/5th November) and then stopped. Inexplicably.


Similar case here, also using Docebo. We have a longer exam of 100 questions in SCORM 2004. It functioned correctly a couple weeks ago. It still works correctly in Firefox. But in Chrome, the LMS is only recording 60 out of the 100 questions. This prevents it from being marked as complete. I also put in a support ticket with Docebo, but I'm not sure if the issue lies with the LMS, Articulate, or Chrome?

Ryan Brown

Hello. I am a SL author using SL360 on the Cornerstone LMS and was curious if there was any new/additional information about this. Is Articulate recommending any best practices for Submitting Results, Completion, and Exit triggers? Lauren mentioned above that SL content published to SCORM (2004 3rd ed?) is not impacted and I wanted to see if this was still the case.

Melanie Sobie

Hi Ryan, I also use Cornerstone. We received an email from Cornerstone yesterday with information. Your LMS Administrator should have received the email. Here is an excerpt:

"What we’re doing to help - In response to these changes, Cornerstone is updating our SCORM player to ensure that SCORM courses continue to communicate user status correctly to our system."

Katie Riggio

Happy Tuesday, all!

I'm excited to share that we just released Update 35 for Storyline 360. What's inside: 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.

To see all the enhancements this version has to offer, follow these steps to update your software! 🎁

Katie Riggio

Hello there!

For folks using Storyline 3: We just released Update 9 that offers support for the Google Chrome 80 and synchronous XHR scenario. This update ensures your AICC courses always communicate a final status to your LMS.

Here's how to update Storyline 3 to the latest version, and we'll continue to update this discussion on any new developments regarding this context for Studio and Rise 360!

Lecours Intégration

I received an email from TalentLMS with this warning.

If I publish in Scorm 1.2 or 2004, does this affect my courses?

I just want to know if I should republish all my courses after the last Storyline update? Because...

Ashley Terwilliger-Pollard

Hi Mat and Christina, 

Some authoring tool vendors may be using synchronous XHR in their SCORM/xAPI output, but we've confirmed with our team that Articulate content only uses that in the AICC output. 

So, you should both be safe with your SCORM output from Articulate. 

I'd also recommend checking with your LMS admin or provider to see if your LMS uses synchronous XHR so they can update your system before Chrome 80 is released. 

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.