UPDATE (2/18/2020): We've released a Hotfix to fix this issue. For more information refer this document.
An update to Google Chrome, expected in early February, may prevent final course tracking and completion status reaching your LMS.
Google has announced changes to the browser, beginning with Chrome 80. As of this version, expected in February 2020, synchronous XHR will be disallowed during page dismissal when the page is being navigated away from or closed by the user. (In other words, when a learner closes a course by closing the browser window, or by going to a new page, some of the background commands that might previously have been used to send final scores to your LMS will no longer be enabled in the browser.) This involves the following events (when fired on the path of page dismissal): beforeunload and unload.
For more information, see Chrome Platform Status.
The communication between content and the LMS can be classified into two levels:
- The communication sent from the content.
- The communication sent from the LMS engine (sent by your LMS providers/services).
As far as Adobe Captivate is concerned, the good news is, that, this change is not likely to affect SCORM 1.2 and SCORM 2004, and AICC standards from the content side. We have, however, identified scenarios with xAPI content where Adobe Captivate uses these synchronous calls to update course tracking. Course tracking that happens in the final few seconds, before the learner closes the browser tab, might not get communicated to the LMS.
We are working on a solution and will update Adobe Captivate course creators as soon as the fix is available.
The problem may also impact your LMS if it uses synchronous calls on page unload). This issue should be addressed by your LMS provider.
For more information, see the post from Rustici Software.