Forum Discussion
Chrome v83
It seems the latest version of Chrome (v83) may not be working with RISE SCORMs. When you close the browser, the session does not close properly, and progress, time, grades, or anything else is lost.
Is this happening to someone else? Maybe it is an already adressed problem?
Thank you very much!
Thanks for letting us know you're hitting this problem, Sakura. We'll update this discussion when the issue is resolved!
We are experiencing this on Moodle 3.7. Our RISE courses were uploaded as SCORM packages several months ago and have been working reliably. In the last two days we have received a flood of users saying they can't complete our courses. No changes in scorm content or Moodle OS.
Thanks, Jim. Our team is having a look at this problem, and I'll post an update in this discussion as soon as I have new information to share!
Same issue in SuccessFactor LMS with chrome browser, there is no communication at all.
Hello, just want to join in with this discussion as we are experiencing this problem as well. When people have finished the e-learning they receive an error message that they have not met all the requirements of the course. Our LMS is Successfactors. We have also noticed something that Mark mentioned in a post above ("When they choose the exit option within the content, it appears that the progress is being saved correctly. It is only when they click the ‘X’ of the browser window that this happens.")
We have currently put a hold on all e-learning roll-outs and content import whilst we were trying to work out the problem but we actually need to roll out some material quite urgently so very much looking forward to hearing a solution.
Would advising all users to use Mozilla as their browser be a good temporary solution do you think?
Hey folks,
Thanks for sharing what's going on with your Rise 360 content. We're having a look at this behavior, and we've seen that making this adjustment in Chrome 83 has helped in some LMS environments:
1. Open Chrome browser
2. Go to chrome://flags/#allow-sync-xhr-in-page-dismissal
3. Change the drop-down selection from "Default" or "Disabled" to "Enabled"We'll let you know if we are able to make changes to Rise 360 output that would help.
We know this work around but this cannot be provided to 50K users internally and many users externally. This needs to be fixed at course level so that the pages can communicate both synchronous and asynchronous way with the LMS. Do we have a solution at rise during publishing level to select these 2 options during publishing SCORM/AICC output.
Thank you for the update, we are now looking into it. But just want to say that we totally agree with SibaPrasad Padhi, we do need a structural solution to this issue which is causing big problems for us right now.
We are optimistic that a Moodle revision to 3.7.6 may fix our issue (we are using 3.7.2). Testing on our development platform showed the problem resolved. Our next scheduled maintenance window on our production server is next week. I'll update when we see what happens.
This is the solution we are currently offering customers, and it has been working for them.
1. Open Chrome browser
2. Go to chrome://flags/#allow-sync-xhr-in-page-dismissal
3. Change the drop-down selection from "Default" or "Disabled" to "Enabled"This same issue is happening with Storyline 360 too. Changing the settings in Chrome helps but as someone else noted, this isn't feasible to ask end-users to make the change. We need a SCORM solution.
Agreed Jennifer - we can't direct our clients to make this change to their browsers.
