Hi David

No I don't recall having seen this before - and having just tested against the latest release on Safari/iOS10 it's all working fine for me.

Is this happening in a very specific setup i.e. only on a particular LMS or in a particular browser?

He Joseph Replin! I don't think that you require to know anything more after Matt reply. Actually I even strive to focus like those topic where informative answer are given through expert. If you want to some amazing knowledge then I like suggest you may check software development company UK from where I keep getting help for my numerous projects.

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.

I've spent the last few weeks looking into workarounds regarding IOS, as my own content requires multiple nested IFrames in order to work.

IOS has huge problems regarding how it displays absolutely positioned content. This is caused by the way it treats the entire IFrame as a viewport (visible part of the page), where other browsers look at the visible part of the page.

There's an extension Called IOS fix that should help with that. alternatively, you can edit the JavaScript within the modules triggering the overlays to replace the overlays with alerts when on IOS.

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.

Hi Dawn

Be happy to help if you could provide a bit more information beyond 'it simply doesn't work' and 'it isn't compatible'.. that's not much to go on ;-)

I do know we've created content in Adapt for Oracle Learning Management before and those courses worked fine on desktop browsers.

(They didn't work on mobile devices but that was nothing to do with Adapt - at that time that LMS used Java for SCORM communication - and the Java plugin isn't supported on iOS or Android)

Thank you all.

It seems some of the woes were coming from the iOS whatsitmaflip!

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.