Scroll Bars Appearing When inserting Videos from Website
Jun 01, 2017
Hi!
We've had to link to website videos to decrease the file size of a large Articulate 360 project. Problem is, we can't figure out how to get rid of the scroll bars. We decided to embed an HTML page with a video player and have the HTML page load the MP4 (based on advice from this forum)
These are the steps we took.
- Insert video with this embed code:
<iframe width="1280" height="640" scrolling="no" src="
https://clscontent.bcg.com/YSNASLearningCenter/WhyStrategyIsImportant.html" frameborder="0"></iframe>
Video H 640 px W 1280px - Create an HTML file (attached) and put it in the same web folder as video.
Video plays but we cant get rid of scroll bars! We thought the scrolling = "no" would solve the issue but not.
Any suggestions would be much appreciated!
Best regards,
Steven
5 Replies
Is your web object at least 1280x640 pixels in size on your project canvas?
And is your SL project's overall size greater than 1280?
Hi there, I'm experiencing a similar issue to the one detailed above, but in Articulate Rise 360. We host our videos on a separate platform then embed them in our Rise courses via an iframe code. Late last year a vertical scrollbar started appearing on the RH edge of these videos in Rise, for no apparent reason. I was able to temporarily workaround it by increasing the pixel height in the embed code from 450 to 470. However, the issue now seems to have got worse as 470 is no longer working - I have to increase to 475, and then this seems to cause some black bars to appear on both sides of the video instead. I've attached a screen shot and would very much appreciate Articulate's help with this issue!
Hi Emma!
Our team would love to help! It would be best for us to work in a support case so that we can find a quick solution. You can reach out to our team here: Connect with a Support Engineer
Thanks Lauren, so sorry not to get back to you sooner on this - I was convinced that the issue was solely with the embedded video player, but those developers have now asked to discuss the issue with Rise to investigate it further - I'll request a support case as you suggested.