Storyline 2 HTML5 - submit interaction when timeline starts not working.

Jun 27, 2016

I have a question where the interaction should be submitted automatically, and I have tested the "submit interaction when timeline starts" in Flash and it is working, but it does not work in HTML5.

Any thoughts?

5 Replies
Katie Riggio

Hi Gerald!

I'd love to look into this with you. First, here is a quick recording of what I'm seeing happen in the published HTML5 output: When clicking on the Next button, the following two interactive slides are skipped and the next slide is a blank Results slide.

Are you looking to have learners submit the drag-and-drop slides and then have their results show at the end? If so, I made this tweak to the file:

  • Changed 'Submit sequence drag-and-drop when the timeline starts on this slide' to 'Submit sequence drag-and-drop when the user clicks Submit

Check out this short video to see how this change works, and the source file is attached below if you'd like to explore its bones.

Let me know if you have something else in mind. I'm happy to dig deeper!

Gerald Sitchon

Hi Katie, Thanks for responding. This story file I've uploaded was just a part of a quiz module where learners need to pass multiple sets of quizzes. Those slides that has Sequence Drag and Drop serves as a gate after the last 2 question bank slides. We don't want users to interact in those drag and drop slides.

A work around we did was create cue points at .5 secs and replaced the "submit  sequence drag and drop interaction when timeline starts" to "submit interaction when timeline reaches cue point.

What we wanted to know is when we publish the course as Flash/HTML5;

  1. why the "submit  sequence drag and drop interaction when timeline starts" trigger works in Flash enabled browser(IE11 and Chrome) but doesn't work when flash is disabled in IE11 and Chrome(FLash is disabled by default in Chrome)? I've uploaded this in SCORM cloud and the same result. It works when flash is enabled and doesn't when flash is disabled.
  2. Is Articulate going to include this in their roadmap of bugs to fix or they will just give up on it just like the list of animations that doesn't work in HTML5?

 

Walt Hamilton

Gerald,

I suspect that it is a timing problem that has something to do with flash, especially if you have animations or transitions.  Your cure (jump when timeline reaches .1 is probably the best for a lot of reasons.

AS to your comment "give up on it just like the list of animations that doesn't work in HTML5?".  You do realize that the finished project uses HTML to display in a browser, and that Articulate doesn't really have any control over either HTML, or any browser's limitations?

This discussion is closed. You can start a new discussion or contact Articulate Support.