Built-in Disabled State: Why would an item still be able to have its HOVER effects if it's been disabled?

Jan 10, 2018

Hi -- We have buttons that get triggered to go to the built-in disabled state after visiting the section that they take you to. When you return to the main home page, that button should no longer be active. However, you can still hover over it and see a hand and the hover state still activates. Is that normal for an item that has been changed to disabled?

Also, the built-in disabled state wasn't automatically grey, is that correct? We had to change the color to something specific ourselves. I assumed the built-in state would be automatically grey, but maybe that only works for BUTTONS and not for other objects we've turned into buttons? 

11 Replies
Lewis Ward

Hi Ashley,

I had the same issue as you this morning, it's quite frustrating. What i did find however is that the buttons work as they should when you publish it. So no hover states on disabled buttons until the button changes to a state of normal.

Doesn't really resolve your issue but at least in future you won't have to delete and rebuild elements!

Qasem Parvez


I have created a trigger for the next button to be enabled once the timeline has ended, however the hover state is still active while the button is disabled. Please could you let me know how I completely disable the button so the user is not able to hover over it. See attached file for an example of the button.

Crystal Horn

Hi there, Qasem. I'm seeing this behavior on objects that are grouped or have multiple objects added to the Normal state. I'm going to document it for my team to review.

In the meantime, can you work with your custom button ungrouped from the shape, and without the additional object in the Normal state? The Hover state won't be activated on independent objects that are in the disabled state.

Katie Riggio

Hi Nancy!

Thanks for writing in, and sorry to hear that you're facing this problem.

We'll let you know as soon as we know more. When a bug gets reported, here's how we tackle it:

As we continue to investigate, would you be willing to share the .story file with us? We're happy to troubleshoot your file for any custom solutions!

Maria Costa-Stienstra

Hi, everyone!

We appreciate your patience while our team investigated this.

I am happy to share some great news! We fixed the issue reported where:

Modern Player: Disabled Prev Next buttons still have hover state

Be sure to install the latest Storyline 360 update (Build 3.49.24347.0) to take advantage of all the recent features and fixes. 

If the problem happens again, please let us know, or you can always work directly with our support engineers here.

Jason Butler

Hi - I've found a simple workaround to fix the issue with custom buttons that are compiled of grouped objects. If you create a button from a group containing for example a text box, icons, images and a background shape, you can create states for it as you would a traditional button (normal / mouseOver / disabled). 

Then place over the top in your slide a transparent button - and use this to control your custom button states. If you need to disable the button - simply hide or disable the transparent button, and set your custom group to it's disabled state. The mouse will not  revert to a cursor when it rolls over and the button will stay disabled. To the end user the effect is seamless and you can have complete granular control of the button states via triggers and variables.

I hope that helps.