Web object too big for player

Jul 02, 2014

Hey guys,

At times, we are having issues when I put a web object (a linked video in this case) into a course.  When the course is opened, the video is bigger than what I placed in the course.  In the past, this required an update to Flash and the problem was fixed.  However, we currently have a few computers that continue to have this issue even with updated Flash, Silverlight, etc.

This is a problem because the enlarged video hides buttons (including the next button on the player) that a student needs in order to move forward.

Any ideas would be greatly appreciated.

Thanks!

4 Replies
Christine Hendrickson

Hi Kristin,

Web objects appear above other content, so if they're larger than the player and the slide, they'll hover over those items. 

Here's more information:

Articulate Support - Player Elements Appear Behind Web Objects

Now, if you're making sure that the web object isn't larger than the slide or player, this may be something we should check out.

If that's the case, are you able to share the .story file here?

Thanks!

Christine Hendrickson

Hi Kristin,

Thanks for sharing the file!

One problem - is the video/web object hosted on an internal server? I'm not able to load it in Chrome or Firefox. I even attempted to visit the URL (http://streaming/Alcohol%20Misuse/High/) outside of Storyline and the page does not load. 

If that's the case, it's going to be a little difficult for me to test this. 

I did publish and upload the course, just in case you want to test it on your end:

http://chendrickson.articulatetest.com/forumfiles/KristenStephenson/story.html

I also cannot tell how you're viewing the course. I see that you have Chrome and Internet Explorer open, but cannot tell which browser you're using or if the course is located on a web server or LMS. I think I see "local" in the address, but I cannot be certain. It blurs after a bit of zooming in :)

Can you take a look at the link I shared and let me know if you see the same behavior? 

Thanks!

This discussion is closed. You can start a new discussion or contact Articulate Support.