Thanks for sharing that here - and I was easily able to replicate it following your steps so I've reported it to our QA team for additional review. I am unable to offer a time frame in regards to when I'll hear back from them regarding a fix, so please continue to use the workaround (that you also provided here) and once we have additional information to share we'll post here.
This goes wider than the javascript trigger text editor. I see the same issue for the Value field in a trigger. you have to delete the string (or replace with completely different characters), save the trigger, then re-open, type new string, and save again. otherwise case changes are not saved.
7 Replies
Hi James,
Thanks for sharing that here - and I was easily able to replicate it following your steps so I've reported it to our QA team for additional review. I am unable to offer a time frame in regards to when I'll hear back from them regarding a fix, so please continue to use the workaround (that you also provided here) and once we have additional information to share we'll post here.
this is a known issue, only fix is to delete trigger and recreate
Thanks Phil - I didn't see it reported for Storyline 2, so I did pass along to our team.
Holy cow. I've been adding JS triggers like a madman and I haven't noticed it. Thanks for the heads-up.
It carried across from SL1 I kept finding it as I always get case wrong
This goes wider than the javascript trigger text editor. I see the same issue for the Value field in a trigger. you have to delete the string (or replace with completely different characters), save the trigger, then re-open, type new string, and save again. otherwise case changes are not saved.
me too!
This discussion is closed. You can start a new discussion or contact Articulate Support.