LMS Bookmarking and Completion Status Failures when a Browser window is closed.

Chrome 80 will “Disallow synch XHR in page dismissal”

Chrome 80 will “Disallow synch XHR in page dismissal”

January 16, 2020 – updated December 30, 2020

Chrome 80 discussion link here


When the user clicks the close button on the internet browser window the course performs a final call to save progress, variables, and completion data to the LMS.  This is a call to the LMS and is a common action of e-learning software.  Most browsers (Chrome version 80+, Edge, and Firefox) will no longer allow the LMS to save data using the current typical method.  As a course administrator, you may see that student progress, course variables, or completion status are lost when the student is using one of these browsers.  

Technically, the SCORM course calls APIs in an LMS’s SCORM Player to save course data. The LMS SCORM Player is responsible for ensuring data is saved to the LMS, not the SCORM content / course.  So IF the SCORM Player is using synchronous XHR requests (known as the Chrome 80 change) during page unload then the LMS needs to do something different.  Most LMS providers have used this method.

For AICC the course is responsible for sending data to the server. If you use Lectora read the Resolution section below.


LMS data recording of content published for xAPI, AICC, and SCORM.


Customers will encounter this issue only when students: 1) are using browsers Chrome version 80+, Edge, or Firefox, and 2) they close the course with the browser window’s Close button (usually the x).  


SCORM: LMS providers may need to modify their systems to ensure data is saved.  SCORM courseware will not have to change or be republished.  

AICC: Please use the most recent version of Lectora Inspire and Publisher version 18.2.2 or greater.  Lectora Online users, republish AICC titles that have not been published since February 3, 2020.  

xAPI: Most xAPI statements are sent when actions happen, if you are using cmi5 it might require some changes. We encourage authors to create exit buttons within the course and direct students to use these course exit buttons.

Action required:

AICC: For AICC only, all AICC titles will need to be republished using updated versions of Lectora and Lectora Online.  As of February 3, 2020, the update has been applied to Lectora Online.  For Lectora 18 users, please use version 18.2.2 or greater.

SCORM: Inquire with your LMS provider if they have updated their LMSCommit() function to resolve the synchronous XHR request change in Chrome 80.  If they have implemented a change, then you should not have any further issues. If they have not implemented any change, then please use the alternative below.


If you have an old LMS running SCORM or cannot republish your AICC content, you might want to register with Google for a temporary exception for your LMS.  You can register here:

Suggested Workaround:

  • Authors should design courses to have a final 'I am done' button with an Exit / Close action and encourage / require a learner to click it prior to closing a browser window.
  • Users should be directed to 1) not close courses using the browser window close button or 2) use an alternative browser.

Information for other Learning Management Systems


Based on the following information, we suggest that Moodle users run the most recent versions of software available.  Please note this information is provided for the convenience of our users, eLearning Brothers has no influence on the Moodle platform.

  • Moodle versions 3.5.11, 3.6.9, 3.7.5, 3.8.2 are noted as having addressed the primary issue related to the changes in Chrome 80.  Details can be reviewed here:
  • There are some continued issues with SCORM failures when running Chrome 80+ identified with Moodle versions 3.5.10, 3.6.8, 3.7.4, 3.8.1, 3.9  Details can be reviewed here:
  • It appears that improvements implemented 11/21/2020 for Moodle master versions 3.5, 3.8, 3.9, 3.10, 3.11 may provide a final solution.

    This article last reviewed Dec, 2020. The software may have changed since the last review. Please visit our Release Notes to learn more about version updates.