iPAD HTML5 issue...

Mar 10, 2014

Keith Trodden
By Keith Trodden

Hi all,

I am wondering if anyone out there can shed light on this technical issue...

I have built a demo in Articulate Storyline.

Here is the link to it:-

http://www.datamark.org.uk/storyline_demo2/story_html5.html

It has 3 slides with the last 2 being links to web objects on my server which are HTML5 files with some interactivity. 

The last slide Part 3 has this link for example:-

http://www.datamark.org.uk/HTML5_examples/interactive2/index.html

On a PC in the browser these links work fine and I can click on the buttons OK

BUT...

On the iPAD, http://www.datamark.org.uk/HTML5_examples/interactive2/index.html

works fine. However, this web object doesn't seem to work so well through the storyline file

(http://www.datamark.org.uk/HTML5_examples/interactive2/index.html). I can't really click the buttons.

Does anyone have any ideas?

Thanks in advance...

Keith

3 Replies
Ashley Terwilliger-Pollard
10 years ago03/10/14 at 9:54 am (UTC)

Hi Keith,

Thanks for sharing these here - I tested both on my iPad mini with iOS7 and on my Windows 8 laptop - and both behaved the same. I did noticed that some of the buttons on the second interaction did not behave as I would have expected them too - regardless of where I tested. For example, on the map of England where it says "click for a close up" just brought me back to the first image? Also the green buttons on the images which look like prev/next buttons had the same behavior. 

If I'm misunderstanding the problem or what you're experiencing could you please share a bit more information here with us? 

Ashley Terwilliger-Pollard
10 years ago03/11/14 at 8:25 am (UTC)

Thanks Keith for the image - when using the iPad you'll want to use mobile Safari or the mobile player app. Chrome is a the supported browser for testing HTML5 content on your desktop or laptop. For more information on supported browsers for viewing content please review this tutorial.  I was testing it in Mobile Safari on my iPad which is likely why the buttons were working correctly for me. 

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