Forum Discussion
RISE 360 - Refresh iFrame manually to load content in LMS
Hi CraigSmith-ff78,
Happy to chime in!
You can test your course in SCORM Cloud to see if the behavior you're experiencing is specific to your LMS. Here are my recommendations:
- Update Storyline 360 to the latest version
- Upload your course to SCORM Cloud
- Change this setting in the Launch Behavior section to simulate the course opening inside an iframe
If you can replicate the behavior in SCORM Cloud while using Storyline 360's latest version, please share a copy of your project file here or in private by opening a support case so we can test and analyze what's happening. We'll delete it when we're done!
Hello JoseTansengco ! Thank you for the suggestion, I was unaware that SCORM cloud allowed us to select a launch type. I can confirm that there are no issues with the course in SCORM Cloud when setting launch type to frameset. Which is very odd, as I can't see any distinct differences between their setup with this option toggled on and ours.
I would be questioning whether our SCORM API was to blame but these courses work fine in our LMS when we open the course in a popup window. The fact that it works in a frame with a manual reload makes me think this must be some race condition but I've made no further progress towards figuring out the exact conditions that trigger it.
I would also be questioning my sanity if not for the fact that Kevin is experiencing the same issues in an entirely separate environment (SuccessFactors). Our LMS is required to work on local servers without an internet connection, so we cannot use third-party SCORM providers' services.
If you are willing to work with us to investigate further let me know, we can ask one of our client's content provider to build a course without sensitive information and setup a testing environment that we can share with you. For now, we have built a toggleable hack to reload the frame so they can continue using Articulate courses.
Hi Craig_Smith,
Thanks for sharing the results of your tests. Since your course works properly when launched as an iframe on other platforms, this usually means the issue is LMS-specific and has nothing to do with how the course is published. I'd recommend working with your LMS support team and sharing the results of your SCORM Cloud test with them so they can check why your course doesn't work properly when launched as an iframe on their platform. They'll be better positioned to help with LMS-specific behavior.
Hello Jose, note that while it works on SCORM Cloud, Kevin reported an independent example in an entirely separate environment that reproduces the same issue. I would expect additional reports in the coming weeks.
I am part of the Ripple Operations LMS development team, this issue was brought to my attention by our support team. I have thoroughly debugged our API and display environment and nothing seems out of order. The errors included in my original message are non-descriptive in nature and originate from your package's minimized bootstraper.min.js script making it nearly impossible to trace the root cause. Hundreds of other SCORM courses in our system remain fully functional without the need for this hack rendered within iFrames.
If you can provide us with an unminimized version of boostraper.js I may be able to better trace the origin of the issue. Otherwise we are at a loss as to how to proceed. Luckily these courses remain functional with the addition of the aforementioned refresh hack.Should anybody else stumble upon this thread, this is roughly what we see when the error occurs in iFrames.
Note that other customers have reported similar rendering issues with the next button and other navigation buttons (also fixed by a manual refresh of the frame) but the course remained otherwise functional.
Hello JoseTansengco ,
We have identified the source of the issue and recommend you discuss this with your engineers if it is expected behaviour.
The rendering issues occur only when an articulate course is initially rendered in an iFrame wrapped in a container that has `display: none` on it (not the frame itself). Our loader displays the frame wrapper at a later time.
We have found a workaround:visibility:hidden; height:0; width:0;that functions much like display:none but does not trigger the issue.
Get in touch if you need a hand reproducing, at craig@rippleoperations.com.Hi Craig_Smith,
I'm glad you could get it to work in your LMS, and thanks for sharing what fixed it for you. We'll monitor if other users report this issue to see if more LMS environments are affected. This will help to confirm that the behavior isn't specific to SuccessFactors.
