Our preparations for Chrome 80
There are changes in the 4 February 2020 update to the Google Chrome browser that may impact elearning content viewed on Chrome. There will be no impact on other browsers, such as Firefox, Safari, or Internet Explorer. We proactively patched our systems in October 2019 and have been working with our publishers and Learning Management System (LMS) partners to ensure a smooth transition.
Since releasing the patch, our testing has revealed no negative impact on OpenSesame content, and the OpenSesame player is performing as expected.
Changes expected in Chrome 80
What’s changing? Up until Release 80, Chrome has allowed webpages to send data immediately when a visitor closes a page or navigates away (as “synchronous XHR”). Chrome has also provided a security tool for cookies (“SameSite=Lax”), but has not been enforcing that as a default setting.
Release 80 will no longer allow pages to send such data when a visitor leaves. Google’s reasoning is that the activity harms performance and there are better alternatives. (Details here.) The release will also make “SameSite=Lax” the default for cookies, which is intended to prevent certain types of cyberattacks. (Details.)
Potential impact on elearning
Why does this matter? If a course was designed to complete or post information to an external URL upon exit, and it was left unpatched, learners using Chrome may experience problems with progress saving or completions registering. Unpatched systems that have relied on the removed Chrome behavior may also fail to read cookies, which could impact progress and completions.
While OpenSesame courses are working as intended, and our systems were patched in October, this Chrome update may affect other elearning providers. We recommend confirming with your LMS (and any other third-party content vendors you might use) that they are also prepared.
If you are experiencing any problems with your OpenSesame courses, please do not hesitate to contact us.