Is anyone else having the problem where the published web files are automatically redirecting to the HTML5 version? It's intermittent and it's not just me--at least one co-worker is also having this issue with their published files. Sometimes republishing fixes the issue.
Hey Keari! Thanks so much for reaching out here. Google introduced a new security feature in Chrome 56 that blocks Flash content unless you give it permission to play. Since you've enabled the HTML5 output, it's going to default to that in Chrome for people running the latest version.
If you choose to not include the HTML5 output when publishing and only want the Flash version available, Google Chrome may instruct your users to Right-click to run Adobe Flash Player when you launch Storyline and Studio courses. This article details a couple ways that learners can handle this new security feature. Again, if you include the HTML5 option when publishing then you won't have to worry about this as it will default to that output in Chrome. This seems to be what you're picking up on in your post, good eye!
I hope that helps clarify a bit, please let me know if you have further questions! :)
Thanks for your reply. It wouldn't be a big deal if the HTML5 version performed as well as the Flash version. I'm testing a course with the HTML5 version right now and grouped items are disappearing for no reason. I've also noticed very fuzzy text in scaled courses when viewing the HTML5 version. The cursor not switching to `pointer` when hovering over certain buttons in the HTML5 version is not only irksome to me as a developer but it also diminishes the user's experience.
You definitely shouldn't see grouped items disappear and the cursor not switching to a hand pointer in HTML5. Would you be able to share your .story file here so we can take a closer look?
4 Replies
Hey Keari! Thanks so much for reaching out here. Google introduced a new security feature in Chrome 56 that blocks Flash content unless you give it permission to play. Since you've enabled the HTML5 output, it's going to default to that in Chrome for people running the latest version.
If you choose to not include the HTML5 output when publishing and only want the Flash version available, Google Chrome may instruct your users to
Right-click to run Adobe Flash Playerwhen you launch Storyline and Studio courses. This article details a couple ways that learners can handle this new security feature. Again, if you include the HTML5 option when publishing then you won't have to worry about this as it will default to that output in Chrome. This seems to be what you're picking up on in your post, good eye!I hope that helps clarify a bit, please let me know if you have further questions! :)
Thanks for your reply. It wouldn't be a big deal if the HTML5 version performed as well as the Flash version. I'm testing a course with the HTML5 version right now and grouped items are disappearing for no reason. I've also noticed very fuzzy text in scaled courses when viewing the HTML5 version. The cursor not switching to `pointer` when hovering over certain buttons in the HTML5 version is not only irksome to me as a developer but it also diminishes the user's experience.
As browsers stop allowing flash this will get worse, the SL360 HTML5 output is much better if you can upgrade.
Hey Keari!
You definitely shouldn't see grouped items disappear and the cursor not switching to a hand pointer in HTML5. Would you be able to share your .story file here so we can take a closer look?
This discussion is closed. You can start a new discussion or contact Articulate Support.