I have a text entry field (I have tried both numeric and text entry) that is not working when published. It works as intended in preview mode but once it's published, the Enter key no longer functions to show another layer. I have removed the fill and line from the field.
I am wondering if anyone can figure out why this isn't working. A previous version of this slide worked correctly. I'm using the most recent version of Storhyline 2.
We have the same Problem. We have published Contents using Storyline 3 and Story 2. The contents were published due LMS long time ago. We use the SWF files. Our Training use a *.aspx plataform. All the contens that have a Press Enter to continue function don't work since the last update . They run under Internet Explorer Update 11.0.49(KB 4052978).
Hello Claudia - So, once the files are published and uploaded to your LMS, you are not sharing the story.html file? You mentioned swf files is why I'm asking.
We do have an issue reported to our team related to the HTML5 output and the Enter Key.
If you hit Enter twice is it working for you Claudia?
I'm bumping this thread because my testing group and I are experiencing a similar Enter key problem as the OP. Except in our case, when the Enter key is pressed with an INCORRECT value in the text entry fields, it's actually kicking us back out to the "Instructions" slide of the simulation (which, it might be worth nothing, is also assigned Home in the Player). If the correct value is present when Enter is pressed however, the trigger works as it should and advances the user
This other thing with this is, that it is only occurring in Internet Explorer 11. It doesn't happen in Preview mode, or when the module is viewed using Chrome. Unfortunately, forcing all of our users to go through Chrome isn't an option for us, as IE is our default company browser.
Really strange that an incorrect answer would send you to a previous slide (and only in IE11!). I can't say I've seen that happen before, so I'm really curious to dig into your file and find out what's going on.
Would you mind sharing a copy of it with me? Also, what version of Storyline are you using?
53 Replies
Hi
We have the same Problem. We have published Contents using Storyline 3 and Story 2. The contents were published due LMS long time ago. We use the SWF files. Our Training use a *.aspx plataform. All the contens that have a Press Enter to continue function don't work since the last update . They run under Internet Explorer Update 11.0.49(KB 4052978).
Could you help us to solve this issue
Hello Claudia - So, once the files are published and uploaded to your LMS, you are not sharing the story.html file? You mentioned swf files is why I'm asking.
We do have an issue reported to our team related to the HTML5 output and the Enter Key.
If you hit Enter twice is it working for you Claudia?
Hi,
I'm bumping this thread because my testing group and I are experiencing a similar Enter key problem as the OP. Except in our case, when the Enter key is pressed with an INCORRECT value in the text entry fields, it's actually kicking us back out to the "Instructions" slide of the simulation (which, it might be worth nothing, is also assigned Home in the Player). If the correct value is present when Enter is pressed however, the trigger works as it should and advances the user
This other thing with this is, that it is only occurring in Internet Explorer 11. It doesn't happen in Preview mode, or when the module is viewed using Chrome. Unfortunately, forcing all of our users to go through Chrome isn't an option for us, as IE is our default company browser.
Hi Richard!
Really strange that an incorrect answer would send you to a previous slide (and only in IE11!). I can't say I've seen that happen before, so I'm really curious to dig into your file and find out what's going on.
Would you mind sharing a copy of it with me? Also, what version of Storyline are you using?
Hi all,
Thanks for your patience while our team looked into this issue!
Today we released Storyline 360, build 3.21.17083.0 which included a fix for the issue where:
Let us know if you have any other questions, we're here to help.
This discussion is closed. You can start a new discussion or contact Articulate Support.