Here's a stickler... I created a SL project and "restricted" the menu: http://screencast.com/t/rjHJGIhnNmD5
When viewed on a PC using the Flash version, it works as expected. However when viewed on an iPad or PC using the HTML5 version, the menu can be used for free navigation.
Per the comparison chart in the link below, the Articulate Mobile Player and the HTML5 content doesn't currently support restricted or locked navigation:
You can check out our updated documentation for Storyline 2 here. This included many updates for HTML5 functionality, including the navigation restrictions.
I used Articulate Storyline 2 trial version to check if the restricted navigation works fine. It did work, but some how messed up bullet colors (last bullets color changed to black from maroon), text spacings for the options in knowledge checks moved and bold text appears a bit elevated from the baseline.
I suspect during the conversion of the .story files from storyline 1 to storyline 2 messes up the text formattings.
this caused me a lot of rework/rechecking on the module and the translated modules as well.
Is there a work around where we can restrict the player menu via javascripts to make it work on ipad? or may be just check if you are getting a update out soon to fix this in storyline 1.
We have a lot of modules built in storyline 1, and now upgrading to Storyline 2 doesnt seem a viable option if it messes up the formattings.
Just need this fixed for HTML5 published versions and not for the AMP.
10 Replies
Hi Steve,
Per the comparison chart in the link below, the Articulate Mobile Player and the HTML5 content doesn't currently support restricted or locked navigation:
http://www.articulate.com/support/kb_article.php?product=st1&id=1568gg1ayot2
Thanks, Brian-
I found that chart shortly after posting. Sorry. I hope this will be enabled soon, as many courses require sequential enforcement.
-Steve
PS Any rumors about when an update to Storyline will be released?.
Hi Steve,
Sorry, we don't release any information on future product releases.
are there any "workarounds" for this issue in storyline?
Tom
Hi Brian,
is this fixed yet, i know this is an old post so i assume it to be fixed in three years time atleast.
Hi Suraj!
You can check out our updated documentation for Storyline 2 here. This included many updates for HTML5 functionality, including the navigation restrictions.
Hello Leslie,
I used Articulate Storyline 2 trial version to check if the restricted navigation works fine. It did work, but some how messed up bullet colors (last bullets color changed to black from maroon), text spacings for the options in knowledge checks moved and bold text appears a bit elevated from the baseline.
I suspect during the conversion of the .story files from storyline 1 to storyline 2 messes up the text formattings.
this caused me a lot of rework/rechecking on the module and the translated modules as well.
Is there a work around where we can restrict the player menu via javascripts to make it work on ipad? or may be just check if you are getting a update out soon to fix this in storyline 1.
We have a lot of modules built in storyline 1, and now upgrading to Storyline 2 doesnt seem a viable option if it messes up the formattings.
Just need this fixed for HTML5 published versions and not for the AMP.
Hi Suraj!
I do not have any information about an update.
If you are having trouble upgrading a project and need us to take a look, please share a file for us to take a look at.
How do i share a file?
Hi Suraj! You are welcome to share here via the Add Attachment option in your reply window, or if you need to share privately you can do so here.
This discussion is closed. You can start a new discussion or contact Articulate Support.