Skip to main content
Participant
May 1, 2013
Question

HTML5 isn't autoplaying

  • May 1, 2013
  • 21 replies
  • 2162 views

When I publish a file as HTML5, it doesn't autoplay.  It is a white screen with a play button in the middle of it.  How can I create the course file so that it autoplays as with a swf output?

This topic is closed to new replies. Start a new post to keep the conversation going.

21 replies

Participant
June 14, 2018

My team currently uses both Captivate and Storyline because we are determining which we will use going forward as our authoring tool.  I've created the same project in both programs and have published them in HTML5.  The Captivate output does not autoplay while the Storyline output does.  I'm using the same browser side by side in two tabs.  If Chrome isn't allowing HTML5 content to autoplay, why does that change only affect Captivate's output and not Storyline's?  It might seem like a small quality of life issue for the end user, but it is a large enough issue to make staying with Captivate a little less appealing.

Lilybiri
Legend
June 14, 2018

Maybe because Storyline's output is not a full HTML output? SL cannot create real responsive projects, does it create HTML projects or are they just playing in a HTML wrapper?  AutoPlay is disabled since quite a while on some mobile devices as well.  Is it not looking weird that Chrome blocks all HTML content from AutoPlay but SL will play? That sounds bit suspicious. How will this be in the future with other browsers?

Look at the whole picture, please! I see many SL users come (back) to Captivate.

Participant
June 15, 2018

I’m using Storyline 3 for my production and yes it outputs full HTML5 as well as fully responsive playback on multiple devices. I’m not trying to start an arguemwnt about Captivate and Storyline. I’m simply saying that, as of right now, Storyline 3 or Storyline 360 has autoplaying HTML5 projects while the newest update to Captivate does not.

Varun Kalra
Participating Frequently
May 1, 2013

Hi there,

Please check this forum thread:

http://forums.adobe.com/message/4587553#4587553#4587553

It seems like a work around.

Thanks.

brooke_s1Author
Participant
May 2, 2013

Thanks!