I have an issue with Rise content displaying more whitespace at the end of a page when shown through the LMS than through Review. The first screenshot is how it is displayed in LMS and the second is how it previews in Rise.
I spoke to one of our developers and he found the following:
"The .page__wrapper class that Rise puts around content has a min-height: 100vh style applied to it which causes the extra padding. It's something Rise puts in so not something we have control of from a site perspective."
This is not my area of speciality so not sure what more to add. We are using Grassblade LRS and I am using the latest version of Chrome.
I have attached the LMS output file here. It is most noticeable at the bottom of the Objectives section.
Thanks for sharing your output, Lyndon. In SCORM Cloud, the padding at the bottom of the first lesson appeared normal to me. Here are some adjustments you can make to try to improve the behavior in your LMS:
Compare launching the course in a new window with launching within the LMS frameset (same window) if your LMS allows you to control the launch behavior.
Try turning off the block entrance animations in course settings.
Hi,
Thanks for the reply.
I tried both solutions and it hasn’t rectified it. Currently we open the Rise module in a new tab, when the learner completes the module they close the tab, which refreshes the dashboard page to show completion.
I will pass this on to our developers and see if they can provide any other insights.
I am getting the same problem in my LMS (Litmos) when importing this file. As well as having two scroll bars. I uploaded the file to SCORM cloud previously and didn't manage to replicate any issues with it.
I've attached an example of my SCORM file for you. Be great if you could help me out!
9 Replies
Hi Lyndon! I can't say I've seen extra white space added to the bottom of a Rise 360 lesson before, so I'm curious to dig into this!
Would you be willing to share your LMS output file with us here? Be sure to include these helpful details:
Hi Alyssa,
I spoke to one of our developers and he found the following:
"The .page__wrapper class that Rise puts around content has a min-height: 100vh style applied to it which causes the extra padding. It's something Rise puts in so not something we have control of from a site perspective."
This is not my area of speciality so not sure what more to add. We are using Grassblade LRS and I am using the latest version of Chrome.
I have attached the LMS output file here. It is most noticeable at the bottom of the Objectives section.
Regards
Lyndon
Thanks for sharing your output, Lyndon. In SCORM Cloud, the padding at the bottom of the first lesson appeared normal to me. Here are some adjustments you can make to try to improve the behavior in your LMS:
Let us know if that helps!
Hi,
Thanks for the reply.
I tried both solutions and it hasn’t rectified it. Currently we open the Rise module in a new tab, when the learner completes the module they close the tab, which refreshes the dashboard page to show completion.
I will pass this on to our developers and see if they can provide any other insights.
[signature
We have changed the global height settings in the Grassblade xAPI (reduced the height to 45%) and it seems to have helped a lot.
We will monitor it for now and hopefully it will continue to work.
Thanks for the update, Lyndon! Let us know if you need any more help with this.
Will do thanks
Hi all,
I am getting the same problem in my LMS (Litmos) when importing this file. As well as having two scroll bars. I uploaded the file to SCORM cloud previously and didn't manage to replicate any issues with it.
I've attached an example of my SCORM file for you. Be great if you could help me out!
Kind Regards,
Matt
Hey Matt!
Thanks for including the output file. I also tested it on SCORM Cloud, and everything looks great there.
Having you tried launching the course in a new window instead of launching within the LMS frameset (same window)?
You may also see a difference if you turn off the block entrance animations in course settings.
This discussion is closed. You can start a new discussion or contact Articulate Support.