Autoplay is turned off for HTML projects. How to improve the workflow for having a better design for the static start screen?
Since I follow the forums daily (and moderate the Jive forum for Captivate) I have seen a lot of threads appearing about version 10.0.1.285 where AutoPlay is automatically disabled for all HTML output, not only for responsive projects like in previous versions. Reason is that the most recent version of Chrome decided to ban Auoplay from all ‘websites’, which means also from eLearning courses running in a web browser.
Focus of any eLearning developer is to offer the learner an engaging, well-designed course, The default look of a published HTML course (responsive or not) with Autoplay turned off is not so nice: blank screen (eventually on a background color matching the later colors of the course) with a default black Play button. A couple of weeks ago I described my workflow to improve that first look by adding a poster image, replacing the Play icon and eventually taking out the dimming of the poster image. If you missed it, this is the link:
However this workflow could be improved.
Feature Requests – HELP!
I live in Belgium with the official motto ‘Unity is Strength‘.
That is also valid for requests to the Adobe Team. The workflow described in that blog post would takes less time if these feature requests were fulfilled:
- Being able to use one of the slides as Poster image.
I logged this feature requests several times, even when only publishing to SWF existed. At this moment you need to create the poster image which can be done by taking a snapshot, but pointing to a slide would be quicker.
- Being able to have several Play icons, to replace the Play icon by a custom graphic, or at least to be able to edit the colors.
For the workflow I described Administrator rights are needed to replace the original Play icon in the installation folder by an empty icon.
- Being able to edit the dimming percentage of the poster image.
At this moment you need to edit the Alpha percentage in the CPM.JS file created in the published folder. Reason for that dimming is to make the default Playbar button stand out from the background poster image. If the second feature request is realized, where you can replace that button by a custom button, the dimming percentage is not that important. But with the described workflow the image for the Play button is part of the poster image and that looks strange.
Please, take a minute to launch this requests. You can use my texts, no problem. Here is a direct link to the request form: