Hi Bill

I don't know quite at what version of iOS this started occurring but I have noticed an annoying bug that's certainly present in iOS  v11.3.x (iPhone only) where, if the SCORM debugger that Moodle/Totara has is enabled, I can't – initially - get it to launch the course at all.

When happens is that Safari prompts you to allow the debugger window to open - but then if you switch back to the main window to get the other prompt (which annoyingly you have to do now since Apple changed the way the allow/block prompts appear) my iPhone just doesn't show it; my iPad, however, does!

If you then leave the debugger window open then try reloading the other page, the course window opens fine and loads no problem – presumably because with the course debugger window already open it only needs to display one allow/block prompt this time.

I've just tried a few Adapt courses on Totara and - when the SCORM debugger is switched off - I haven't had any issues and certainly haven't seen any 'could not connect to LMS' issues - though I am using a relatively old version of Totara (2.9.12)

One thing I have noticed in the past is that occasionally when you use the 'click here to launch this course manually' link (rather than the Enter button) you get a 'could not connect to LMS' error... I think the last time I investigated this it seemed that Moodle/Totara was not actually making the LMS API available at the point the course was loaded and started looking for it. Whenever this happened I noticed that Moodle/Totara would include a sort of weird countdown message in the course window prior to actually going to the course content. Typically, I can't replicate it now despite following the same steps!

It looks like the LMS in question is Moodle, it's therefore likely to be displaying the course in an iframe which causes problems with responsive content like Adapt on iOS as documented here and here.

You need to install/enable the spoor extension.

You can use the launchNewWindow extension to get your course to open itself in a new window on iOS, thereby avoiding the iOS/iframe problem.

You're using responsive to two different ways... It's a little confusing. You want the iframe to size itself correctly (responsively) and you want the scrolling to work properly (to respond to user input)... I think?

There are a whole lot of reasons why you should give up, and may I suggest that you do?

Take a look at adapt-launchNewWindow. This is really the only solution to your problem - forcing the content to load in a new window on ios.

But... If you really want to get your head around why you should do that...

Look at adapt-moodle which was my original attempt to do what you're suggesting... it modifies the parent window of the iframe to inject javascript and css to make sure the iframe is responsive in size relative to it's parent (you have to size the iframe in pixels otherwise they take the content height and not the window height). Second to that, you need to stop using the html+body tags to do scrolling inside the iframe... because that's broken... instead the wrapper should be moved inside a container div which manages the scrolling, which means you need to hack jquery.scrollTo to stop it taking the window.scrollY, and use a bit of -webkit-overflow-scrolling: touch to get the smooth scrolling working... you can see that in action in adapt-iosScrollFix.

Even after those suggested fixes, you're still going to have position: fixed issues (which means trickle, navigation bar and notify problems) css rendering issues, general laggyness and lots of rerendering, layout thrashing, tearing, etc etc, ios was never really designed to support iframes with scrolling content...

If you've got nested iframes... god help you... :/

Kind Regards,

Ollie.

I have tried a couple of the CSS suggestions mentioned in various forums, but that does not seem to make any difference.  I don't have access to the server to start changing code in MOODLE.

Unfortunately it seems the answer for our learners for the time being is not to use iOS devices for learning.

Have you tried any of the suggestions in the thread I mentioned before?

Hi

Thank you for the reply, it makes the issue clearer,  I appreciate you taking the time.

We recently upgraded to MOODLE 3.2, which is when the issue seemed to get worse, prior to that ADAPT content did seem to work ok.  I was not sure if this was a particular issue since MOODLE 3.2 or if iOS had suddenly got worse due to a software update, either way it seemed to happen about 3 months ago...

I have tried a couple of the CSS suggestions mentioned in various forums, but that does not seem to make any difference.  I don't have access to the server to start changing code in MOODLE.

Unfortunately it seems the answer for our learners for the time being is not to use iOS devices for learning.

Chrome for iOS is essentially just Safari for iOS with a different user interface. Apple don't allow any other browser rendering engine other than the built-in webkit rendering engine to be added to iOS.

You didn't find a definitive answer in your search because this isn't really any one single solution - other than to amend Moodle to open the course in way that doesn't use iframes. That's what Totara (enterprise version of Moodle) does - it's called New Window (Simple) and works very well.There's some discussion around how that can be done here.

Unfortunately iOS-Safari's handling of iframes is just really poor, some of the problems with it are listed in this post (that whole thread is worth reading btw). Last time I checked there were 741 open issues mentioning 'iframe' on webkit.org - some have been kicking around since 2006 :-(

AFAIK it has been a problem since Moodle 2...

Hi

I did to a search, but there does not seem to be a definitive answer.

I assume the problem is something to do with iFrames, though it does happen in the google browser for iOS also.

 - Is this a recent problem as the courses used to work?

- Is it to do with MOODLE or something in a recent iOS update?

- Is there a way to fix it?