Forum Discussion
Storyline 360 Review Feature supports Javascript?
Hi all
I am new to the whole review feature in Storyline 360, and what I really want to know is - will it support Java Script?
I need to add a volume/audio bespoke feature which uses Java Script - will this feature work in the Review when i send it out to the clients?
So far it doesn't seem to be but I wondering if I did something wrong with my Javascript
Cheers
28 Replies
Yes it is related to the Javascript in the MasterSlide. I copied it and checked it to see if i could quickly find what was wrong with it, but its quite elusively coded. What i see is, its a script from cluelabs.com to customize the player.
Checking the player only thing it does ( as i can quickly see ) is changing the player's background color and the UI-icons color. For that you donot need to use cluelabs scripts. That can be done in the existing CSS of Articulate.
Lets see if i can quickly find a workaround so you can abandon the cluelabs script.If for some reason you need to stick to the cluelabs script... they should fix it then ;-)
Thank you. Thought as much. Just using cluelabs as it created the script for me. If you’re looking at a workaround, i’ve always wished that script would include a visited state for menu items. Cluelabs said they couldn’t help when i asked. Only if it’s easy of course. You’ve already helped so much and we wouldn’t want your wife getting the wrong idea!😉🤣
Get Outlook for iOS
Not quite clear what you mean with the visited state...but its possible for sure. If you use the css as attached above... you can remove the javascript of Cluelabs. Your title will have the correct background color in the player. Glad to help anytime... my wife understands ;-)
If you replace your generated CSS file with this one after publishing. Then your player is as you made it with cluelabs script.
Thanks
Hi Katherine,
Probably its some inconsistency in the trigger and the variable. Hard to tell what exactly without the actual Storyline. If you share that, i can check.
Kind regards,
MathHi Math, I thought the file would attach from sending the attachment in the reply email but it didn't - here it is now. Thanks again for your help.
As suspected its a typo...
commit in undercast and for TextEntryCommit12 its entry too as undercast.I would advise to simplify your variable names else this kind of mistakes might happen again...
Instead of TextEntryCommit1 - 12 use input_1 to input_12
Less options to type something wrong.I can't believe I didn't spot the typos - I looked and looked and looked. Thanks for the advice Math. I will simplify variable names in future.
When testing as Web in the browser. Use CTRL + Shift + I ( or F12 ) to open up the Browser console. All errors will be logged in the console below. There i immediately spotted 2 missing variables...then it was easy to check naming on them.
