Forum Discussion
Trigger editor remains locked to Execute JavaScript after adding a JavaScript trigger
In the current Storyline build (3.126.38052.0), after creating an Execute JavaScript trigger, the trigger creation interface no longer allows other trigger action types to be selected. The behaviour persists across layers/slides in the project. Previously created native triggers continue to function. The current JavaScript interface also does not appear to provide the script naming/selection functionality available in earlier versions.
Does anyone have seen the same problem or do you have a solution?
Thank you.
Carmel
2 Replies
That's a genuine bug, not something you're doing wrong. Restarting Storyline clears it, like you found.
One thing worth doing: file it with Articulate Support (with your build number) so it's logged as a defect. Forum posts don't automatically become bug reports, and a stuck trigger editor in the current build is the kind of thing that needs to be on their radar.
To get out of the javascript lockup that prevents the creation of other triggers, I had to quit Storyline and restart the application again. The script will stay and other triggers can be created. But once you create another javascript trigger, the lockup happens again.
