There seems to be an issue with the player on iOS. Like a MAJOR bug
I set a trigger to disable the Next button when the slide begins, and another to enable it when the slide ends.
This works correctly when viewed on a Desktop browser. However, on a mobile browser the buttons are ALWAYS enabled.
If I use restricted Navigation (and apply it to the Next button) then the Next button is disabled until the play head reaches the end of the timeline, where is enables.
This is fine for slides that don't require user action, however, this will not work if I want to have the user click several buttons before advancing, for example.
Why can't I control the navigation buttons via trigger in mobile Safari/Chrome?
We had a bug where the Disabled Player Navigation Buttons changed to Normal state when viewed using tablets and mobile phones, but the fix was released in Storyline's Update 66 (July 2022)
5 Replies
Hi, Randall.
Thank you for reaching out!
We had a bug where the Disabled Player Navigation Buttons changed to Normal state when viewed using tablets and mobile phones, but the fix was released in Storyline's Update 66 (July 2022)
To take advantage of this update, launch the Articulate 360 desktop app on your computer and click the Update button next to Storyline 360. You'll find our step-by-step instructions here.
If you have additional questions, please reach out through a support case.
Thanks Maria,
The update seems to have fixed the issue.
Do you happen to know WHEN (what version #) this bug was introduced into Storyline 360?
I don't remember ever having run into this issue before. I may need to republish several courses.
if you had audio in your previous courses, you'll have to recreate them all anyway, otherwise they won't start in firefox >= 103.
Another reason it would help to know WHEN these bugs were introduced.
i totally agree - i even tried to get old storyline installers from articulate recently to find out for myself - unfortunately they said no.
Update:
- in the version Storyline 3.25 (February 26, 2019) i found the firefox bug
- version 3.19 (August 2018) same error
Jürgen