SL2 Seekbar Glitch

I've worked with lots of modules over the years, but I've never seen this one. On some slides in a current SL2 module, I'm seeing the seekbar do this (both Web and LMS output):


There is no rhyme or reason, except for the fact that it may only show on slides which I've disabled/hidden the Next button on (for all the good it does, since it still shows even when hidden). I haven't checked all of those slides, but it looks like it may be the case, and shouldn't have anything to do with this weirdness.

Any ideas?

5 Replies
Alyssa Gomez

Hi Rich,

This is a new one for me, too! I can't say I've seen this happen before, but I'm curious to dive in and help you sort this out.

First, did you host the published content on a web server or a learning management system before testing it?

Also, does this happen in all web browsers or certain browsers in particular?

Katie Gokhshteyn

Thanks for the extra insight, Rich! I'm with you both. This is quite an oddity! 

Is this happening with one specific project or multiple ones? Additionally, could you share the .story file from the screenshot here? Simply pop it into this discussion by using the Add Attachment button in your reply. 

I'd like to take a close look at all slides–especially the ones where the Next button is disabled/hidden–and try to replicate this behavior. Looking forward to lending a hand!

Rich Cordrey

Thanks for the reply! I've attached a content-stripped version of a couple of example slides that the issue is presenting on. It doesn't occur in the internal SL preview, so a publish is required to see it in browser.

There are a few issues here:

1. The Next button will not hide under any circumstances. Whether through the interface (turning off the Next button) or attempting to use triggers to set the state to Hidden. Doesn't matter if the advancement is set to user or auto. 

2. You can turn off the Prev button just fine, but turning off the Next button causes both problems: the Next button doesn't actually turn off, and the seekbar goes haywire.

You'll see in the file that it's very simple. Nothing complex that should tie things up.

Ashley Terwilliger

Hi Rich,

Thanks for sharing that file with us. I took a look and I saw your example showed the odd behavior in the HTML5 output, but not in Flash. I didn't find any similar behavior in new Storyline 2 files, so I'm not sure how to recreate this. Can you share any more about how you initially created this file and removed items like the next/previous button?  

Also, with Storyline 2's HTML5 output, that's supported in Chrome or Safari. Can you let me know what browser you were testing in? 

I did test publishing your file as well in Storyline 3 and noted that the behavior is not present in Storyline 3's HTML5 output. You can view a link of that here.  I only removed the next button from the first slide and left it on the second. 

Let me know, and we'll continue from there!