Storyline not scaling in iframe properly in fullscreen mode on Chrome on Android.

Dec 22, 2016

Hi, I've found a rather peculiar bug using Chrome (v. 55.0.2883.91) on Android (5.0.1) where Storyline mis-calculates the scaling required when the story is shown in an iframe.

When the module is loaded in an iframe on page where the iframe is the only element in the body of the page, we see the grey overlay with the play button. Clicking this play button goes fullscreen as expected.

The issue occurs when there are other elements on the page, for example a simple <br> tag after the iframe. In this instance, Storyline's .framewrap div has a -webkit-transform property applied to it with a scale value of 0.0360065... our stories are 740px wide, and so the result is a 27px wide story at the very top of the screen.

I've created two basic test pages, one with just the iframe, and one with a line break tag after the iframe:

http://web4co.co.uk/articulatetest/iframeonly.html

http://web4co.co.uk/articulatetest/iframewithbr.html

Can you help determine if we're doing anything wrong or whether it is in fact a bug in Storyline?

Many thanks

Mark

3 Replies
Ashley Terwilliger-Pollard

Hi Mark,

Thanks for reaching out here and sharing a link to your course as well. The links you shared looked the same to me, so I'm not sure what I'm looking at? The placement of the slide and the bottom looking cut off appeared in both.  I know the display within an iFrame is something that has caused display difficulties in the past as the iFrame takes control of the content's placement. Depending on how the iFrame behaves, content might appear to be misaligned, cut off, or even have scroll bars. 

Some learning management systems (LMSs) display content in an iFrame by default. If your content is misaligned or truncated in the LMS iFrame, you could also look at how that same content appears when uploading to SCORM Cloud which is an industry standard for LMS testing and this article will walk you through some testing steps.  If the same behavior doesn't occur ther,e you'll want to share that with your LMS team. If you do see it there, please send a copy of your .story file to our Support Engineers here and they'll be happy to take a look at the course! 

Mark Oxley

Hi Ashley,

Thanks for getting back. The difference is only noticeable on Chrome running on Android, but you can emulate what's happening by opening the page in Chrome, opening the Developer Tools, and activating responsive device mode with Ctrl + Shift + M, then refreshing the page. This adds the 'Android' tag to the User-Agent string.

Pressing the grey play button makes the content go fullscreen as expected on the version with simply just an iframe within the body tag, but on the version with an additional <br> tag, the content shrinks as mentioned.

This is not about LMS's, this also happens with simply exporting for Web. All we want to happen is for the content to behave as you'd expect most content to behave when fullscreening an iframe element, which is does for desktop browsers fine, but not for Android.

The Story only has a button which is there to exit fullscreen, but this still happens on a completely fresh project.

SCORM Cloud does not help us as it opens the course in a new window, whereas our aim is to view the course within the LMS, giving people the option to go fullscreen if they want.

I hope this helps clear up what we're trying to achieve :)

Cheers

 

Mark

Ashley Terwilliger-Pollard

Thanks Mark for that additional information. I'd like to get our team testing this one to take a better look at the scaling and how it's behaving in those Android environments so I've opened up a support case on your behalf (using the email address associated with your ELH account here) and you'll receive an email from our support team shortly requesting project files and some additional information. Please keep an eye out for that email! 

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