Transitions - not recognizing triggers on slide

Jan 30, 2015

Technically, I see that transitions are independent sequences between slides.

If I set a slide trigger to disable the next button in the player controls and I have set that slide with a transition, the next button is enabled for the brief time the transition plays. This allows the user to skip the slide.

Is this a bug or is a feature request needed?


19 Replies
Robert Mann

This was probably an oversight since I can see how it technically operates now.

Currently they behave ahead of any slide "logic". This can be problematic particular if you also have dynamic content appearing in the slide based on slide triggers.

If transitions could be engineered as an overlapping behavior to slides rather than a segment between slides, that would be preferred (and would likely resolve these issues I have brought up).

                 ---- transition----

--------slide--------||--------slide--------                                                {preferred}




--------slide--------|---- transition----|--------slide--------                    {current behavior}



Helen Jones

I just brought a SL1 project into SL2 and the first thing I noticed is the Next button doesn't work (the first time) where I've added conditions to the Jump to next slide trigger.  Removing the condition allows the Next button to work.  I deleted the original trigger and then created it again (and the basic trigger works) but adding a condition (a shape has to be equal to Normal before the Next button works) causes it to not work (unless you hit Prev first!)  Thoughts?

Robert Mann


This discussion is directed more to an issue with transitions.

However, there were improvements made in SL2 relating to the navigation buttons. What you may be experiencing is your logic working around limitations in SL1 now competing with improvements in SL2. I am probably giving you little to work with here, but I think it is important to know about how these improvements may be a factor in what you are experiencing. 

Leslie McKerchie

Hi Kristy and welcome to E-Learning Heroes :)

Thanks for reaching out and letting us know that you're running into a similar issue. It looks like the conversation here is a bit dated and was specific to Storyline 2.

I do see a similar report for Storyline 360 that our team is looking into. I've added this conversation to the report as we track user impact and so that we can share any updates with you here.

I wanted to share some information on how we define bugs and how we tackle them when they occur.

In the meantime, we have a couple of workaround options listed:

  • Avoid applying slide transitions.
  • Modify the trigger that will change the state of the button from when the timeline stars to when the timeline reaches 0s.
Katie Riggio

Hello, Richard!

I'm sorry that the bug Leslie shares above is still open in Storyline 360. If anything changes, we promise to share the news here.

If you're in a bind, we'd love to try to help you work around it. Use this link to connect with our Support team.

Soren J Birch

Hi, bug still there. If they take 6 years to not yet handle this bug, I think we can assume it has either been forgotten, ignored or promoted as "WAI". I dont know if it works like this in Modern player, as I only work with the Classic.

I have found a work around: you must either remove transitions (bad) or disable Player navigation around the slides that leads to the transition slide when you need to restrict learner control (less bad). I don't like removing the Next button as it messes with UX and learner expectations - but I guess this is the only choice.