Player size issues on ipad

May 02, 2014

Hello!

I'm working on developing tablet based training to be delivered primarily on ipads (though might perhaps be access from a desktop on occasion).

I've tried every combination of settings as far as the browser and player size, and have followed a few ideas as far as project size that I found on other threads here, but nothing changes when I access the module through our LMS.

Does anyone have experience using Cornerstone as an LMS to deliver training on ipads? 

Here is a screenshot of what happens when we start the module.  There is white space on the left side, and the player controls are not visible.  If we resize the browser, the player controls are visible, but there is still wasted space. 

As of right now, all I can think to do is to include the menu....but the menu font is too small to be usable on an ipad.  There are workarounds in editing the player.css after the fact (thanks to those involved in that thread!), but it's still not an ideal solution, as it takes up real estate that could be used for the actual content.  We're going to be doing a lot of register simulations, so having space always taken up by the menu is far from ideal.

Does anyone have any thoughts on how to help us with this issue? Could it have anything to do with how the LMS, Cornerstone, controls browser windows?

Thanks!

Allison

1 Reply
Ashley Terwilliger-Pollard

Hi Allison and welcome to Heroes!

Do you know if Cornerstone forces the content to display in an iFrame? There is a known issue currently where that content won't display correctly in Mobile Safari, and our team is looking into it. With that being said, since every LMS has a different player set up, it's also worth checking with your Cornerstone team to see if there are any ways you can force it out of the iFrame. You may want to test the course at SCORM Cloud as well and see how it displays there and share that information with your LMS team, as SCORM Cloud is an industry standard for testing SCORM content. 

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