iPad: Several tabs on button required to respond in HTML5 output

Oct 20, 2014


We are encountering issues with Presenter 13 output viewed in mobile Safari: For iPad, it needs multiple tabs on navigation buttons to respond and act accordingly. This seems to be a known issue which is already fixed in Storyline (Update 5) but we urgently need this to be fixed for content developed with Presenter 13 too. 

Thank you,


11 Replies
Graham Francis

Can this be passed to the 'Beta' team as it's pretty important stuff re:
pressing buttons not working etc?

Graham Francis


The SIP School and WebRTC School (Vocale Ltd companies)

26 St. Laurence Road
B31 2AX
United Kingdom

Ph1: +44(0)8709747748

Fax: +44(0)8709747751

Mobile: +44(0)7973500507

Web: www.thesipschool.com /



FollowGraham on Twitter

Join The SIP School on

Join WebRTC School on Facebook

Reply to
iPad: Several tabs
(presses) on button required to respond in HTML5 output

Ashley Terwilliger replied:

Hi Graham,

This issue is still with our QA team for additional review, so I don't have
any updates to share at this point, but we've included this thread in the
existing report with our QA team so that we'll be able to update you here
when there is additional information to share.

Ashley Terwilliger-Pollard

Hi Graham,

I'm not sure what you mean by the Beta team - our QA team are the ones who review things that we or users have found as bugs and look at potential fixes. This is currently in their hands, without any additional information to share here yet. 

Also, I wanted to let you know that when you reply via email your signature is included, so you're welcome to edit the post and remove that information if you wish. 

Ashley Terwilliger-Pollard

Ah! So in this scenario, we're saying the same thing - that our QA team. It's been shared with them, but I don't have information to provide in terms of updates on where their testing standards or if there will be a fix in the next update. I'll keep you posted here with any other information once it's available. 

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