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

When you say "it needs multiple tabs on navigation buttons . . ." do you mean multiple presses of the finger? The "multiple tabs" is confusing.

Hi Mark,

Yes, exactly this! On mobile devices. one has to press the button several times to have the button finally respond and do action (like, continue with next page, send result, go back,...). 

Any ideas?

Hi Silvia!

Are you running iOS8 on your iPad? 

This is an issue that our QA Team is aware of and will be working to correct.

Is this fixed yet as today with newly published content - I still need to press buttons such as 'Next' multiple times to get a response.?

Cheers, Graham

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. 

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

Graham Francis

CEO

The SIP School and WebRTC School (Vocale Ltd companies)

26 St. Laurence Road
Birmingham
B31 2AX
United Kingdom

Ph1: +44(0)8709747748

Fax: +44(0)8709747751

Mobile: +44(0)7973500507

Web: www.thesipschool.com /
www.webrtcschool.com

sip:graham@thesipschool.com

skype:vocale.it

FollowGraham on Twitter

Join The SIP School on
Facebook

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.

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. 

Re: the Beta team - I meant the team that works on the next updates to
Articulate, there is normally a round of bug fixing / testing before a new
update comes out and I was hoping that this bug could be included.

Graham Francis

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. 

Ashley

Has this issue been fixed yet? 

Thanks, Lynne

Hi Lynne,

This issue is still with our QA team for Presenter - and you can see the documentation here regarding this issue.