Using a broadband WiFi connection with 2Mbps throughput, my iPad loads subsequent HTML5 pages so slowly that it becomes ambiguous whether the NEXT button was successfully pressed or not.
Users then repeatedly press the NEXT button in an effort to get the next page to load. The result is that pages in the course are skipped. This is avoidable and bad UI.
Since HTML5/Safari requires the NEXT button to play audio (a restriction unique to iPads), the PREV/NEXT once clicked should be disabled, then re-enabled when the next page begins.
I've seen this problem as well with HTML5, though it's unclear as to why it takes HTML5 output so long to load.
One way to prevent this is to add your own custom back / next buttons and add a loading overlay in a layer on the master slide. Trigger this with your custom next / back nav and it'll show a custom loading overlay that prevents a subsequent click. Serves double-duty 1) providing an indicator that *something* is still happening and 2) preventing impatient clickers (pretty much everyone, ever) from gumming up the works.
Last multiple platform deployment I did used this setup. I rarely use the built-in navigation controls. Custom stuff looks better and is less work than it seems. The bonus is it's within my control
I put mine in the master slide. There's a trick to getting them to actuate, depending on what you want to do. I've done this with a toggled boolean and a listener or simply using an incremented numeric. That way you can connect the buttons to your base timeline.
Error on Next button trigger when viewing on iPad (HTML5) - Republishing after storyline update 3
From one of the slide (slide5), when clicking on the next button, it skips a slide (slide 6), from slide 7 it goes back to the skipped slide (slide 6). I've double checked my setting and it is all set up the exact same way as the others. What can be a problem here? Please help~
Basically it goes like this below:
Slide 5 > Slide 7 > Slide 6 > Slide 8 > Slide 9 > etc. (everything works fine from here)
8 Replies
I've seen this problem as well with HTML5, though it's unclear as to why it takes HTML5 output so long to load.
One way to prevent this is to add your own custom back / next buttons and add a loading overlay in a layer on the master slide. Trigger this with your custom next / back nav and it'll show a custom loading overlay that prevents a subsequent click. Serves double-duty 1) providing an indicator that *something* is still happening and 2) preventing impatient clickers (pretty much everyone, ever) from gumming up the works.
That workaround is a fair amount of work and also revises the appearance of the course on desktop computers which is the lion's share of students.
While a workaround may help in a pinch, it is clear that there is a UI issue in HTML5 that should be addressed in Storyline.
Last multiple platform deployment I did used this setup. I rarely use the built-in navigation controls. Custom stuff looks better and is less work than it seems. The bonus is it's within my control
Steve,
Question about your navigation buttons... Will they work from the Storyline master or do you need to add them to every page manually?
Sam
I put mine in the master slide. There's a trick to getting them to actuate, depending on what you want to do. I've done this with a toggled boolean and a listener or simply using an incremented numeric. That way you can connect the buttons to your base timeline.
Error on Next button trigger when viewing on iPad (HTML5) - Republishing after storyline update 3
From one of the slide (slide5), when clicking on the next button, it skips a slide (slide 6), from slide 7 it goes back to the skipped slide (slide 6). I've double checked my setting and it is all set up the exact same way as the others. What can be a problem here? Please help~
Basically it goes like this below:
Slide 5 > Slide 7 > Slide 6 > Slide 8 > Slide 9 > etc. (everything works fine from here)
Thanks,
Susie
Hi Susie,
Any chance you can share the .STORY file here, or send it over to us privately?
Thanks!
Will do that now. Thanks.
This discussion is closed. You can start a new discussion or contact Articulate Support.