Forum Discussion
Tabbing and disabled buttons
I can verify this bug is still an issue in latest version. You don't need a shared file to verify, just add an element (shape, text box, whatever).
Add a trigger to Go to Next slide if the element is clicked.
Set the element's default state to disabled.
When you test, you correctly won't be able to click the element (cause it's disabled), but you can tab to the element and then press enter to 'click' the 'disabled' button and advance to the next slide.
Not the first time a fix has been applied, only to be omitted and overlooked in future versions.
Hi Shane,
So sorry you're hitting this snag, and thanks for sharing the steps you took to recreate the issue!
Here’s a quick recording of my experience in Storyline 360 Update 3.49.24347.0 after following those steps. I used a button in my test, which has the Disabled state built-in.
A few questions to help us find a fix:
- Does the problem happen during preview, in the published output, or both?
- Is it project-specific?
Would you be willing to share the troublesome file with us? It’ll greatly help our team verify whether that bug is affecting your course or if something else is happening. Simply use this case link.