Forum Discussion
Articulate Rise not saving progress for learners
Hi, I came across this the other week when I was looking at browsers and LMSs for a different reason.
'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.'
Is it possible that the behaviours that people (course not appearing completed) are experiencing is hooked into their browser or browser settings or something like that, that is associated not with Articulate, nor SCORM correctness in the hands of the developer, but in the users' system or in an individual's particular browser configuration.
I am raising this as we've had some weird stuff with users on our platform (Litmos/SAP) that we eventually tracked down to the configuration of the user's browser, in some cases due to security settings put in place to protect the organisation.
We also had some weird stuff, this time with video conferencing person-to-person where notionally identical device configurations worked differently with different callers, some being able to use voice and some not. Again, we tracked the problems down to different security settings buried in the dark recesses of users' browsers.
Long shot I know, but is it, possibly, a browser issue?