3) on iPad (iOS7) it works fine running from a standalone server
4) HOWEVER: on iPad running in an LMS (SCORM Cloud and SumTotal) the audio slider play/pause button is not there, and the reset button goes out of position. (The slider itself still works)
This issue has been reported to our QA team in regards to the HTML5 output in Mobile Safari, and I believe it was fixed in the Update 1 of Storyline 2 here.
I see that this issue is still with our QA team in regards to courses hosted in an LMS only, but the web server fix was included. Is that where you're seeing this behavior still? If so, I will add this thread to the existing report filed with our QA team so that they're aware of other users being impacted and so that I can provide any updates here.
We're only seeing this issue on LMS. Everything works fine when published to web and hosted on our FTP site (even when published for LMS). It doesn't show this issue until it's uploaded to the LMS.
Hi again, Ashley. Just to try to be as helpful as possible, I've also submitted a support case. My number is 00443328, in case you'd like to follow along.
Also, currently seek bar is a set of play/pause, timeline bar and replay button, cant we have all the controls selected separately as per our requirement. I mean if i want to remove pause and play button from the storyline player just like the way we can add or remove next and prev button from the player.
This would have help me designed the player better by adding all my controls inside the slide area, and would have kept only timeline bar of the player as it is.
This is a known issue documented here and slated for a fix in a future update of Storyline. I don't have a time frame to share in regards to that issue, but we'll share any updates here once available.
In regards to your other question, there is not currently a way to separate those player elements. You may want to look into creating your own player with the Storyline SDK or share your thoughts in the form of a feature request here.
Articulate Storyline 2 Update 5 is now available for download. It includes WCAG 2.0 support, several new accessibility features, better HTML5 performance, and bug fixes. Click here for details:
10 Replies
Anybody else see this problem, or have any ideas how to fix?
Hi Roy,
This issue has been reported to our QA team in regards to the HTML5 output in Mobile Safari, and I believe it was fixed in the Update 1 of Storyline 2 here.
Have you installed the most recent update?
Hi everyone,
We've updated our Storyline 2 version to the most recent versions, and we're still seeing this issue.
Hi Nick,
I see that this issue is still with our QA team in regards to courses hosted in an LMS only, but the web server fix was included. Is that where you're seeing this behavior still? If so, I will add this thread to the existing report filed with our QA team so that they're aware of other users being impacted and so that I can provide any updates here.
Thanks, Ashley!
We're only seeing this issue on LMS. Everything works fine when published to web and hosted on our FTP site (even when published for LMS). It doesn't show this issue until it's uploaded to the LMS.
Thanks for your help!
Nick
Hi again, Ashley. Just to try to be as helpful as possible, I've also submitted a support case. My number is 00443328, in case you'd like to follow along.
Thanks for your help!
Nick
Thanks Nick - it is a known issue right now - but that'll help us continue to investigate it and we'll be able associate your case with the QA report.
Hi Ashley,
Would like to know if any update on this issue.
Also, currently seek bar is a set of play/pause, timeline bar and replay button, cant we have all the controls selected separately as per our requirement. I mean if i want to remove pause and play button from the storyline player just like the way we can add or remove next and prev button from the player.
This would have help me designed the player better by adding all my controls inside the slide area, and would have kept only timeline bar of the player as it is.
Thanks for your help!
Regards,
Thariq
Hi Thariq,
This is a known issue documented here and slated for a fix in a future update of Storyline. I don't have a time frame to share in regards to that issue, but we'll share any updates here once available.
In regards to your other question, there is not currently a way to separate those player elements. You may want to look into creating your own player with the Storyline SDK or share your thoughts in the form of a feature request here.
Hi All!
Articulate Storyline 2 Update 5 is now available for download. It includes WCAG 2.0 support, several new accessibility features, better HTML5 performance, and bug fixes. Click here for details:
This discussion is closed. You can start a new discussion or contact Articulate Support.