Objects set to "Visited" initial state do not respond to clicks.

This goes beyond what might seem logical at first, we have to think in terms of how Storyline works. When only the "Normal" and "Visited" states exist, setting the initial state to "Visited" causes Storyline to treat the button as if it has already been clicked, and doesn't respond to clicks again (because the built-in logic says, "you’ve already done this"). Storyline assumes it shouldn’t behave like a fresh (clickable) button anymore. The "Visited" state isn’t just visual, it also signals to Storyline that the button has already been activated. As a result, any trigger attached to it may not fire.

Now, the reverse logic:

When you add a "Disabled" state (even if you never actually use it), Storyline starts treating the button differently. It’s almost as if it thinks, "Hmm, this button could potentially become disabled, so I better check whether it actually is." As a result, Storyline re-evaluates whether the button should still respond to clicks.

Of course, this is just my interpretation. It’s not something officially documented or confirmed by Articulate. Just an attempt to explain what seems to be happening.

JudyNollet​ Lol...I’ve already got a few hats lined up...I just rotate them between bugs like this