Adapt Learning Community: HELP! Cornerstone courses not displaying properly

Hi Jonathan,

This is a well known issue, there is plenty of information about ios on the forum if you search for it https://community.adaptlearning.org/mod/forum/search.php?search=ios&id=2.

Generally this thread seems to be the endpoint for most people https://community.adaptlearning.org/mod/forum/discuss.php?d=926#p4714.

The summary info is that ios support for scrolling content inside iframes is terrible. The only acceptable solution is to launch a new window to remove Adapt content from the iframe. This can be achieved with a simple launch.html page which opens a new window using index_lms.html or by using an extension like https://github.com/cgkineo/adapt-launchNewWindow.

Kind Regards,

Ollie.

Show parent | Reply

Thanks for your pointers – we've used the Launch new Window extension: extremely thankful that it exists… Whilst working through this we also tested the builds launching from Scorm Cloud and the original error does not occur. We're not getting any help from Cornerstone to be honest and the course settings dialogue is limited compared to SC so that'd suggest Cornerstone launches a window differently than SC. Whilst we're sorted right now, does anyone have any experience of configuring a course in Cornerstone to do without the LNW extension? Or is it just a bit rubbish?

Show parent | Reply

We have an LMS expert who's off on holiday until the 29th. I'll email him this thread.

I suspect Cornerstone probably doesn't have an "open without iframe stuff" option. I gather that iframes are pretty standard for most LMSes.

We'll find out when on the 29th no doubt.

Kind Regards,

Ollie

Show parent | Reply

Hello!

Actually with Cornerstone it's such old code it's actually using a <frameset> rather than an <iframe>...! Causes much the same problems with Safari though.

No, I know of no other workaround aside from using the launchNewWindow extension. You only need to configure it to activate for iOS though.

And yes, SCORM Cloud doesn't use either <frameset> or an <iframe> which is why it all works fine there.

Show parent | Reply