Problem with Text Entry fields not recognizing the Enter key

Dec 04, 2014

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.

53 Replies
Amelie BO

Hello Crystal,

I have fixed one of my two issues, but the Enter key still doesn't work properly when I used it as a trigger to submit an interaction. However, when I import my exercise/simulation into a new project, everything seems to be working fine. Any idea on why that could be ?

(I am using SL2 and I'm publishing my course on a LMS)

Thank you! 

Crystal Horn

Hey there, Amelie.  If importing into a new project keeps everything working, I wonder if the original project has an element that became corrupted for some reason.

So were you able to bring all the slides from the original project into a new one, save it, and now it's working?

Also, you're welcome to share your malfunctioning .story file here for us to have a look, too!

Ashley Terwilliger-Pollard

Great news!  We just released another update for Articulate 360, and included a few important fixes and new features that you'll see in the release notes here.  

The item you'll be interested in is the fix for the Enter key not working in courses published for CD.

Just launch the Articulate 360 desktop app on your computer and click the Update button for each application. Details here.

Please let us know if you have any questions, either here or by reaching out to our Support Engineers directly. 

Lauren Pyskoty

Hi there! First time posting :)

I just wanted to follow-up and see if anyone is still experiencing this issue. The text entry was working for us prior to the July 19th patch/update for 360. We now have to press the enter key twice for it to advance to the next screen in our modules, when before we only had to press the enter key once (as it should function). It also only works if the user enters in the correct text entry, clicks outside of the text entry box, then clicks back inside and presses the enter key.  This isn't really true to life for our software simulation projects.

We don't use the text entry as a free form question slide either.

Thanks for your help!

Alyssa Gomez

Hi Lauren, and welcome to the community! So glad you joined us. 😊

I'm sorry you're running into this trouble! We found an issue in HTML5 where data entry boxes with a condition require the learner to hit the Enter key twice, and it sounds like you're seeing the same thing.

Could I take a peek into your file to verify that it is related to the bug we've found? You can share it here in the thread, or you can click here to share it privately

Ashley Terwilliger-Pollard

Hi James,

What conditions do you have associated with the text entry triggers? The issue connected with this discussion is how a user must hit Enter twice in HTML5 output when the trigger has a condition on it. 

If you want to share a copy of your .story file or a screenshot of all the triggers we may be able to offer some alternative ideas. 

Chantel Nicolay

Hello everyone having text entry problems.  I am using Articulate 360 and having this same problem when we try to e-mail or print the text entry field.  It appears to be stripping out the formatting.  I created a project in Storyline360, but then add it to Rise to create a webpage for our learners to take notes.  Unfortunately, this will not be a good user experience, so I will need to look at a back-up way.  The platform created in Rise has the slides of the power point presentation, the place for the learner to take notes, and finally I embedded our audience engagement app, so the learner could tie all the pieces of the education together on one page per session.

You can view it here:

Please let me know if there is anything I can do, I need to demo this on 12/15.




Chantel Nicolay


The note-taking session is the part that would need to be e-mailed or printed for the learner, it is the middle section of the session within each activity in the link I provided above.  Looks like a notebook.

I would like the returns to show up in the e-mailed and printed version, currently it just runs together.  The printed version does allow for a space when you press enter and go to the next row of text, but the e-mail does not, just a run-on sentence.

Thanks for getting back with me, if you need the storyline file to look deeper into this, just let me know.





Ashley Terwilliger-Pollard

Hi Chantel,

Thanks for the info.

The variables  you're using will be grouped together, and doesn't support the line spacing/paragraphs upon displaying it as a variable reference or within the print/email. So perhaps instead you'd want to look at creating individual fields for the text entry so that the user could create paragraphs that way? 

This discussion is closed. You can start a new discussion or contact Articulate Support.