We have created multiple courses in Rise and posted them to our LMS. During testing, after completing the courses, if we go back into the courses, non-text elements tend to load slowly, and if we scroll beyond any element before it loads, the page goes blank, and we have to refresh the browser window. If we scroll very slowly and wait for each element to appear before scrolling further, the page doesn't crash. This happens with Firefox but not Edge. The elements still load slowly on Edge, but we can scroll past them. Also, we have tested with turning off the Block entrance animations. We still encounter the issue.

I believe this issue ("After completing course then returning to it, pages go blank in Firefox") is due to Rise not correctly waiting for synchronous commit requests. The SCORM spec requires commits to be synchronous so that the sco can confirm that commits were saved to the LMS.Modern browsers discourage synchronous ajax/fetch requests and in particular you can no longer make synchronous requests now during window close in any modern browser (this is why having a Save & Exit button enabled in your published course is so important).ScormCloud and some others have taken the pragmatic approach that their scorm player needs to move to async requests. For some time now (maybe the last 18 months) your browser console would light up like a christmas tree in FireFox with react state/memo errors whenever you tried to navigate to a different lesson *after* the course was marked complete due to viewing the required percentage of lessons. In recent versions of Rise, it now does this as soon as you re-open a completed topic. It appears that Rise not only doesn't wait for the synchronous commit requests to complete, but simultaneously seems to need them to complete in order for these state management methods to succeed. While it's near impossible to debug compiled react code, the issue appears to be that LMSCommit is being called simultaneously multiple times when you navigate between lessons. This occurs near simultaneously with other functions that require the result of these commits. If LMSCommit makes async requests it will return "true" immediately and Rise works. if LMSCommit makes sync requests, everything blows up on lesson load. This occurs for me in FX *every* time if I enable synchronous commits and *never* if I enable asynchronous requests, but most people don't have the luxury of having this control. This isn't a bug in the LMS or an issue with the LMS not being "industry standard", in fact even though it's inevitable that we will need to move to async commits when browsers fully remove synchronous requests, I'd argue that this in fact makes LMS like ScormCloud non-conformant in the strictest sense. So to trigger this you need: FireFox (the issue doesn't appear to effect Chromium or Webkit browsers, but I'm not sure if this is due to a quirk which might be fixed in the future or intended behaviour) An LMS that makes synchronous commits (in my experience this is most LMS other than ScormCloud) To have completed the course and then navigate to a new lesson or in more recent versions of Rise to open a completed course in review mode

Hi Adrien, sure, happy to be included on a bug ticket. Cudos to your organisation for mandating FX. If you are serious about privacy and security, it's your best choice. Unfortunately though, there is nothing you can do to address this in your browser settings, it's the code your LMS uses to send the scorm data to the server whenever the scorm package calls Commit/LMSCommit(). To convert your LMS to asynchronous requests you'd need to be able to update the LMS code (the LMS javascript that runs inside your web browser). This isn't a practical solution for most people. It's also not a simple switch as there could be lots of client side and serverside code that is relying on synchronous commits. Given that synchronous commits are part of the scorm spec and for the time being they are still supported by all browsers, it really needs to be addressed within the Rise player. I'll do some testing later today, but I *think* this only effects courses that complete according to a percentage of content viewed. You might be able to get around it with a dummy assessment and a single "Do you want to complete this topic Yes/No?" question as the final lesson and use that as the completion trigger. But that's pretty ugly. I'll try to confirm this and let you know. Andrew

Hi Norman, We have not encountered this in Firefox when returning to a previously completed course. The course loads and behaves normally.

Hi Norman and Karl Same problem here : several load and display bugs on Rise courses published as scorm on a LMS ; and more critical, if the scorm rise course is checked as completed, it's suddenly impossible to reopen and display it : a blank page appears, can do anything on it, just a "mode relecture" (in french, maybe "review mode" in english ?) comment at the top left of the page. This problem seems to be recent, but also affects old Rise courses. Should it be due to a mozilla update ? LMS update ?

Hi, Most Learning Management Systems will automatically switch to "review mode" as soon as a student has completed and passed a course. The "review mode"message you are seeing comes from your LMS, and it should be possible for your LMS administrator to turn it off.

After completing course then returning to it, pages go blank (Firefox)

KarlMuller
Community Member
3 years ago
Hi Norman,

We have not encountered this in Firefox when returning to a previously completed course.

The course loads and behaves normally.
Sectionconcepti
Community Member
3 years ago
Hi Norman and Karl

Same problem here :

several load and display bugs on Rise courses published as scorm on a LMS ;

and more critical, if the scorm rise course is checked as completed, it's suddenly impossible to reopen and display it : a blank page appears, can do anything on it, just a "mode relecture" (in french, maybe "review mode" in english ?) comment at the top left of the page.

This problem seems to be recent, but also affects old Rise courses.

Should it be due to a mozilla update ? LMS update ?
- KarlMuller
  Community Member
  3 years ago
  Hi,
  
  Most Learning Management Systems will automatically switch to "review mode" as soon as a student has completed and passed a course.
  
  The "review mode"message you are seeing comes from your LMS, and it should be possible for your LMS administrator to turn it off.
Sectionconcepti
Community Member
3 years ago
Hi Karl,

Thanks for your reply.

I'll ask my administrator about this.

However, the problem doesn't seems to be this auto switching in review mode : it obviously seems to be an incompatibility between Firefox and the review mode because it works with other browsers like Edge, Chrome, and Chromium.

Unfortunately, using Firefox is mandatory on our organisation computers...
TimS-6c341247-3
Community Member
2 years ago
We are having this same problem. Was a solution ever discovered for this?
CNavarro
Former Staff
2 years ago
Hi folks,

I am sorry to hear that your learners get a blank page when they revisit a completed course in Firefox. I recommend the following troubleshooting steps:

Ensure that their device and browser are fully updated.

Clear their browser's cache.

Restart the device.

You can also test the course with SCORM Cloud, the industry-standard testing engine. If the issue doesn't occur in SCORM Cloud, the issue could be with your LMS. I recommend reaching out to your LMS support team for help.

If the issue also occurs in SCORM Cloud, we would love to take a closer look at your course. You can reach our support engineers here.
Sectionconcepti
Community Member
10 months ago
Hi Chino,

Sorry for the reply delay but I missed your reply notification.

Clearing Browser's cache doesn't works.

I tested with SCORM Cloud and it seems to work, but I can't figure out how the issue could be with our moodle LMS because It works perfectly with Edge and Chrome but not with Firefox...
- JoseTansengco
  Staff
  10 months ago
  Hi Section Conception-Ingénierie SNPS,
  
  Good call testing in SCORM Cloud. I'd recommend contacting Moodle support to check why your course doesn't work properly in Firefox when hosted on their environment. It might have something to do with the player of their LMS. You can also enable the debug mode of your course to check the logs in case an error message is thrown when your course is launched in Firefox.
LucianaPiazza
Staff
10 months ago
Hello Section Conception-Ingénierie SNPS,

Thanks for reaching out when you had the chance with answers to my colleague Chino's questions! Helpful to know that clearing the cache does not work and that all seems to be working correctly in Edge and Chrome.

Since this issue only occurs in Firefox, it seems to be browser-specific and not related to an issue with your course. I recommend contacting Firefox Support to see if this is a known bug they are aware of.

I'll open this post up to the community in case they've come across solutions regarding their experiences in Moodle with Firefox as their browser that they can share.

Hope you have a great afternoon!
Sectionconcepti
Community Member
10 months ago
Hi Jose and Luciana,

Thanks for your replies.

I also think it's browser-dependent and not related to my course or LMS settings.

I'm gonna try to launch the course after activating debug mode and I'll let you know. I'll also contact Firefox support to see if they know this bug.
EricSantos
Staff
10 months ago
Hi Section Conception-Ingénierie SNPS,

Happy to chime in as well! I also think this issue is browser-related since it doesn't occur in other major browsers except Firefox. Have you also tried whether you or your learners are running the latest Firefox version?

If so, it is recommended that you test in your LMS with debug mode enabled and check the Firefox Web console for errors on the page.
AdrienJUILLE267
Community Member
9 months ago
Hi Eric,

Thanks for your reply.

Actually I'm running already latest Firefox version. The problem occurs since more than one year now, so it doesn't seem to be version related.

I checked for errors on the console log using debug mode but I wasn't able to notice any significant error in that file. (But I must admit that I can't understand anything to the language in that debug log ^^ )