A few months ago, we had a customer call in with an issue with a SL2 SCORM 1.2 file. They weren't able to proceed after visiting tabs in the course; the NEXT button that we had programmed wasn't being triggered to appear. We pinpointed this down to being related to SL2 and Firefox. We now recommend that other browsers are used to take our courses.
However, I had a call today from a member who is experiencing the exact same issue with the same course, but he is using Safari on an iPad. Has anyone else reported this issue with certain courses not working with certain browsers?
Do you know any details about the member's iPad? Specifically, are they using Apple iOS 7 or later?
Have you seen this problem in your own testing? I'd be happy to help you with that! Send me a copy of the original .story file, and I'll take care of the rest.
He said that both his iPad and his iPhone - the devices he tried to use - were recently updated. To add to this, I updated my personal phone last week and I WAS able to replicate it - the NEXT button wouldn't appear. I tested this course prior to launch on my phone months ago, and it worked fine, so I think it's related to the iOS update.
The file is attached here - please see if you can replicate. I appreciate your help.
We are specifically talking about the slide with the tabs. Each tab leads to another slide. When clicked, the tabs are changed to "visited" per triggers. Once all tabs are "visited," that is when the NEXT button should appear.
Ah, now I see the problem. On desktop, the next button appears on slide 1.4, but on iPad it does not. I'd like our Support Engineers to weigh in on this, so I'm going to open a case for you (01069881). Keep an eye out for an email from Support@Articulate.com.
I popped in to check on your case this morning, and I wanted to share Abel's findings here:
It seems that the behavior is different when viewing the HTML5 output depending on the device and browser you used. I’ve logged the issue as a possible software bug.
As a workaround, I would suggest to use T/F variable to track each button when clicked and a trigger that will change the state of the custom navigation button to "Normal" depending on the value of the variables. Here's my proposed steps:
Create True/False variable for each button with "False" as its initial value. Then, add a trigger on each button that will change the value of the variable from "False" to "True" when the button was clicked.
Add a trigger that will change the state of the custom navigation from "Hidden" to "Normal" when the timeline starts and with a condition that all variables is equal to "True".
Thanks again for bringing this to our attention, and I'm sorry if it has been giving you headaches! We'll be sure to let you know as soon as we have an update on this issue.
8 Replies
The issue we had a few months ago is linked here.
https://community.articulate.com/discussions/articulate-storyline/storyline-2-and-latest-version-of-firefox-compatibility-issues
Hi there Jackie, thanks for reaching out!
Do you know any details about the member's iPad? Specifically, are they using Apple iOS 7 or later?
Have you seen this problem in your own testing? I'd be happy to help you with that! Send me a copy of the original .story file, and I'll take care of the rest.
He said that both his iPad and his iPhone - the devices he tried to use - were recently updated. To add to this, I updated my personal phone last week and I WAS able to replicate it - the NEXT button wouldn't appear. I tested this course prior to launch on my phone months ago, and it worked fine, so I think it's related to the iOS update.
The file is attached here - please see if you can replicate. I appreciate your help.
Thanks, Jackie. Did you find that the Next button didn't appear on any slide, or on certain slides in particular?
I tested your file on my iPhone and iPad iOS 10.3.1 in Safari, and I saw the next button on both devices.
Give this link a try on your devices, and let me know if you see a difference.
We are specifically talking about the slide with the tabs. Each tab leads to another slide. When clicked, the tabs are changed to "visited" per triggers. Once all tabs are "visited," that is when the NEXT button should appear.
Ah, now I see the problem. On desktop, the next button appears on slide 1.4, but on iPad it does not. I'd like our Support Engineers to weigh in on this, so I'm going to open a case for you (01069881). Keep an eye out for an email from Support@Articulate.com.
Hi Jackie,
My colleague Abel is testing your file now--you should hear back from him shortly!
Hi there Jackie,
I popped in to check on your case this morning, and I wanted to share Abel's findings here:
It seems that the behavior is different when viewing the HTML5 output depending on the device and browser you used. I’ve logged the issue as a possible software bug.
As a workaround, I would suggest to use T/F variable to track each button when clicked and a trigger that will change the state of the custom navigation button to "Normal" depending on the value of the variables. Here's my proposed steps:
Thanks again for bringing this to our attention, and I'm sorry if it has been giving you headaches! We'll be sure to let you know as soon as we have an update on this issue.
This discussion is closed. You can start a new discussion or contact Articulate Support.