But for most of our customers and users it´s not only "a click". There are other developers (and users) saying, no need to make a fuss about a click. Each of our elearning contents consists of up to 100% audio and up to 90% video (and not only a single videofile, but many). As for eLearning and LMS I see things a bit more different compared to simple websites. Speaking about important problems, the switch from SWF to HTML5 is no problem for meīut the autoplay is a big problem IMO. Speaking about websites and ads I totally agree with no autoplay. I will start a discussion about that to get help for other users for those requests. I would love to see the workflow made easier by the Adobe team, have logged several feature requests for this and previous versions. To take out the automatic dimming of the poster image (thanks to a CP-friend, expert in CSS).To design a poster image with a replacement Play icon.To replace the used black button icon by an empty graphic.
Users asked about that workflow and several weeks ago I posted a step-by-step explanation: Since I publish only to HTML since a year, and made the publsihed tutorials available for all devices (using mostly rescalable HTML) where AutoPlay already was turned off for a lot of mobile devices, I did use a workflow to get rid of that awful White screen and the standard black Play button. But I totally understand that the situation for eLearning courses is different and causing problems, because the Chrome ban doesn't worry about the difference between a ormal website and eLearning running in a browser.
Personally I always took out AutoPlay whenever I embedded a CP published course in my blog, even when only SWF was available, because I really dislike websites where audio/video starts playing automatically. The decision of Chorme to ban all AutoPlay has caused a lot of noise, on this forums.
0 kommentar(er)
