Unfortunately there is no way to remove that pop up - as it's built into the preview functionality (similar to reminders about web objects that won't function in preview). If you need to preview your animations, you may want to preview the individual slides using the play button on the timeline or look into publishing it for web and placing it a testing platform like Tempshare.
One way to do this would be to add a condition to your JavaScript trigger and create a variable to drive it.
Execute JavaScript when timeline starts IF finalPublish=true.
Create a variable called finalPublish and set it to false. When you're ready to publish as final, just go into the variable manager and change this to true and all of your JS triggers will run.
One way to do this would be to add a condition to your JavaScript trigger and create a variable to drive it.
Execute JavaScript when timeline starts IF finalPublish=true.
Create a variable called finalPublish and set it to false. When you're ready to publish as final, just go into the variable manager and change this to true and all of your JS triggers will run.
nice that Steve shared with some workaround, but can we please ask for adding an simple option in preferences in future releases? Something like "don't show javascript support in preview". Javascripts are used by more experienced people, and probably on many slides, so they already know that doesn't work in preview and probably are a bit frustrated that they must see that popup many times during the preview. And I think we can agree that's not some big issue to change :)
The above feature is good for some use cases, but I'd still like the global option to turn it off permanently across all courses. Every one of our courses has JavaScript code for music handling and common functions, so we just want to turn the reminder completely off. It's never useful in our use cases.
Dear Storyline Developers, is this really this hard to add a simple tick to not show something again? Come on, please, that's like the simplest QOL improvement you can implement in matter of minutes probably. Please, do this already. That's most annoying thing in whole process of production.
Following Steve Flowers suggestion above, we've added logic to all of our courses to ignore Javascript on slides whenever a variable is flagged (PublishMode is what we call it). It requires all developers to follow a specific convention that we have to teach, but it gets the job done. Since all of our courses use a javascript instrumentation library, music library, and other javascript-based tools, it's the only way to test the courses without significant friction. Without this convention, each slide would prompt developers multiple times during testing.
A simple systemwide setting to turn the alert off would eliminate this additional organizational burden for us. The alert is a "feature" that was only useful the very first time it's ever used and does nothing except cause digital friction for the hundreds and thousands of times it triggers afterwards for a course developer.
A solve would be either a systemwide disable option (preferred) or a persistent non-interactive and non-intrusive banner on the test UI that says Javascript disabled for testing) if you're really concerned about people forgetting about it or need to communicate other things.
One more comment. Jürgen Schoenemeyer's solution will work great, but I don't want to be re-prompted every time I open the story file. One time per Storyline installation or one-time forever. Either of those works well.
To address the issue with animations, you could consider placing a brief loading animation or placeholder at the beginning of your animation. This could help to prevent the "Javascript support is not available" message from interrupting the initial animation sequence.
I would like to keep the warning but don't make it modal, an always on top popup that shows errors, similar to javascript console would be very helpful here. The same popup could show values of variables in realtime.
I would also like to add support for a "less intrusive" JavaScript warning popup.
I really Like Phil Mayor's suggestion. We have experience with other authoring tools and they also had a way to review the live value of variables during a preview (for debugging purposes).
Thanks for reaching out and adding your voice! I've included your feedback in the feature report and will update this discussion as soon as we have news to share!
24 Replies
Hi Luke,
Unfortunately there is no way to remove that pop up - as it's built into the preview functionality (similar to reminders about web objects that won't function in preview). If you need to preview your animations, you may want to preview the individual slides using the play button on the timeline or look into publishing it for web and placing it a testing platform like Tempshare.
Hey Luke,
One way to do this would be to add a condition to your JavaScript trigger and create a variable to drive it.
Execute JavaScript when timeline starts IF finalPublish=true.
Create a variable called finalPublish and set it to false. When you're ready to publish as final, just go into the variable manager and change this to true and all of your JS triggers will run.
Nice solution Steve!
I love that
Thanks for a solution to this Steve
Steve,
I just have to say, you are very rapidly becoming my most favored hero. :-)
This is absolutely perfect!
Thanks,
Bobbi
This post was removed by the author
Hello,
nice that Steve shared with some workaround, but can we please ask for adding an simple option in preferences in future releases? Something like "don't show javascript support in preview". Javascripts are used by more experienced people, and probably on many slides, so they already know that doesn't work in preview and probably are a bit frustrated that they must see that popup many times during the preview. And I think we can agree that's not some big issue to change :)
Thanks for sharing your thoughts Mateusz.
I've submitted a feature request on your behalf.
I also request this feature. The warning is annoying when I see it on every preview if I insert Javascript in a master layout.
Thank you for sharing your perspective, Gary.
I have submitted a feature request on your behalf.
I agree with the feature request. Having the option to turn off these Javascript warnings would significantly reduce the nuisance factor.
Thanks for sharing your perspective, Christopher. We appreciate it!
the best solution - in my opinion - would be an option to select "do not show warning again" when the alert appears
this should be valid until the next time the .story file is opened
The above feature is good for some use cases, but I'd still like the global option to turn it off permanently across all courses. Every one of our courses has JavaScript code for music handling and common functions, so we just want to turn the reminder completely off. It's never useful in our use cases.
I'm back after 5 years of my original post.
Dear Storyline Developers, is this really this hard to add a simple tick to not show something again? Come on, please, that's like the simplest QOL improvement you can implement in matter of minutes probably. Please, do this already. That's most annoying thing in whole process of production.
I agree.
Following Steve Flowers suggestion above, we've added logic to all of our courses to ignore Javascript on slides whenever a variable is flagged (PublishMode is what we call it). It requires all developers to follow a specific convention that we have to teach, but it gets the job done. Since all of our courses use a javascript instrumentation library, music library, and other javascript-based tools, it's the only way to test the courses without significant friction. Without this convention, each slide would prompt developers multiple times during testing.
A simple systemwide setting to turn the alert off would eliminate this additional organizational burden for us. The alert is a "feature" that was only useful the very first time it's ever used and does nothing except cause digital friction for the hundreds and thousands of times it triggers afterwards for a course developer.
A solve would be either a systemwide disable option (preferred) or a persistent non-interactive and non-intrusive banner on the test UI that says Javascript disabled for testing) if you're really concerned about people forgetting about it or need to communicate other things.
One more comment. Jürgen Schoenemeyer's solution will work great, but I don't want to be re-prompted every time I open the story file. One time per Storyline installation or one-time forever. Either of those works well.
To address the issue with animations, you could consider placing a brief loading animation or placeholder at the beginning of your animation. This could help to prevent the "Javascript support is not available" message from interrupting the initial animation sequence.
I would like to keep the warning but don't make it modal, an always on top popup that shows errors, similar to javascript console would be very helpful here. The same popup could show values of variables in realtime.
I would also like to add support for a "less intrusive" JavaScript warning popup.
I really Like Phil Mayor's suggestion. We have experience with other authoring tools and they also had a way to review the live value of variables during a preview (for debugging purposes).
The repeating popup is also an issue for me. Please provide a way to prevent repeated showing of the popup?
Hi Ellie!
Thanks for reaching out and adding your voice! I've included your feedback in the feature report and will update this discussion as soon as we have news to share!
Have a great rest of your week!
Cannot overstate how helpful Phil’s suggestion would be.
Hi Walt I think the warning has been removed because the javascript now runs in preview along with the console.