I am having a problem with the text entry. I would like the learner to be able to type a longer text into the text entry box. When he presses 'enter', a line break should be created within the text entry box. However, as soon as the learner presses the enter key, the text is automatically submitted and the learner is moved on to the next slide. Is there a way around this? I deleted the 'next' and 'submit' button and created my own submit button, but this didn't work either. Can anybody help? Thank you.
Thanks so much for reaching out about this issue, and our team is seeing the same thing. From what we can tell so far, the issue happens when the learner uses the Enter key immediately after typing their answer in a text entry field.
We know this bug is causing a snag for your learners, so our team is taking a closer look at what could be causing this. While I don't have an ETA to offer at this time, we'll be sure to keep you posted on any updates we receive.
Thank you! Oddly enough, I just found a workaround that seems to be ok. If I make the entry box larger to accommodate 3 lines or so, the enter key no longer takes away tabbing on the feedback layer. No idea why, but it's working!
There are a couple of conversations here, and with regards to the original question:
The Enter key will submit a Text Entry question type as you can see in this documentation.
I see that you are replying to Alyssa's last response, so perhaps you are running into the issue shared here about tabbing to the feedback layer. This is still open with our team and I do not have an update at this time. This conversation is attached so that we can provide an update here as well.
I am reaching out to share that the issue where you can't tab to feedback layer items when using Enter to submit text entry interaction has been resolved!
The next step is to update Storyline 360 by heading to your Articulate 360 desktop app and clicking "Update" next to Storyline.
If the problem reappears, please let us know! We are happy to help!
This issue is still happening for me and I have the most up to date version of Storyline. When users are typing and accidentally tap the enter button it submits the slide. I would like to prevent this from happening altogether. Please let me know if there is a workaround.
When there's a data-entry field on a question slide, pressing the Enter key on the keyboard submits the learner's response for evaluation. In other words, pressing the Enter key is the same as clicking the Submit button.
A workaround for this is to add a trigger to the submit button to determine when the user can "Submit Interaction".
If you increase the height of the text entry box to be more than two lines, then the Enter key registers as a carriage return (new line) and does not submit the question.
When there's a data-entry field on a question slide, pressing the Enter key on the keyboard submits your response for evaluation. In other words, pressing the Enter key on the following question slides is the same as clicking the Submit button.
Graded—Fill in the Blank
Graded—Numeric
Survey—Short Answer
Survey—How Many
Freeform—Text Entry
You can press Shift+Enter to add line breaks to short-answer surveys and ungraded freeform text-entry questions when the fields are tall enough to allow multiple lines of text.
Hi Annemarie,
Thanks for the additional information. Does Shift+Enter work for you?
Hi All, I have update my Storyline 360 to the latest version but I'm still having problem with the Enter key not getting the value user type on the text entry. I've set the submit button on the slide & Enter for submit keys. But it doesn't work, when user press Enter key, they're just advancing to next slide. When I want to show their typed value on the last slide, it doesn't show. Can someone help me?
With your permission, I'd like to take a look at your project file to investigate what's happening. You can share it publicly here, or send it to me privately by uploading it here. I'll delete it when I'm done troubleshooting.
I'm running into a slightly different version of this problem. We present learners with a sentence that has no punctuation and ask them to type the whole sentence into the text entry field with correct punctuation. Some sentences are long enough to need two lines, so we make the text boxes tall enough for that. They are allowed 2 attempts. There is a custom submit button on the slide with a trigger to submit the interaction when user clicks submit button.
If learner enters text and presses submit, all is well.
However, if learner enters text and hits ENTER out of habit, that submits the interaction.
The problem is that the ENTER also registers as a linebreak so even if they enter the correct answer, the extra line break makes the answer register as incorrect. When they go back for their second attempt, the linebreak is still there and very easy to miss, so the learner can easily still get the incorrect feedback layer just because they have a linebreak at the end of their answer.
So we need Storyline to either interpret ENTER = submit or ENTER = text entry, but not both at the same time.
It sounds like you're looking for the option to choose whether the Enter key will allow a user to submit a question or add a line break. I'm happy to share this approach with my team.
Currently, when there's a data-entry field on a question slide, pressing the Enter key on the keyboard submits your response for evaluation. Using Shift+Enter will add line breaks. On a content slide, Enter or Shift+Enter adds a line break (return), so you can start a new paragraph.
I did find a workaround that to be honest, is a bit clunky but it does the trick. Here's a quick demo!
To whomever still needs this functionality, I did find a workaround. Essay didn't work for me because we needed people to be able to see and print, if desired, what they entered and what the suggested responses are with the Review Result option. We hope people don't use the enter key, but we can't control what users decide to do.
I will say, it is a little annoying that we have options for how to submit in the quiz form - which is to use a button and (or at least it seem so) to submit with a keystroke. One would assume if that is blank, that a keystroke would be ignored.
That said, here's how I got this to work (you may need to modify it a bit based on your needs):
Note: I used a custom Submit button in the page, but this should work with the player submit button. I did have some extra stuff to suppress the Next button and show the custom submit button until the slide was answered (so on review they can use the Next button) - so this shouldn't change anything - I just mention it in case...
Question type: Fill in the blank (I had a longer entry box) Question properties: Feedback "By Question", Attempts Unlimited
Setup: Create variable FIXEnterPressed (True/False) Add a trigger - change FIXEnterPressed to FALSE when the timeline starts
On the Submit button (on click), add the triggers to adjust FIXEnterPressed to TRUE and then Submit interaction (order is important)
Delete the Correct and Incorrect feedback layers. Make the Try again layer blank (change the master and delete any 'artifacts' that may remain), set the timeline to the shortest time (we really only want it open for a very short time, just to run a trigger)
Adjust Try Again layer properties to: Hide other slide layers (or not, really shouldn't matter), Hide slide layer when timeline finishes, revisiting: Initial State, (others are deselected)
Add a trigger in Try again layer to jump to next slide when timeline starts if (condition) FIXEnterPressed is equal to True
---
So essentially what we're doing here is passing a variable to check when Submit is pressed vs when someone presses Enter. We have to hack it by using the Try Again layer, otherwise the question submits before anything else, so we can't really hijack the logic.
Ideally and hopefully the question properties will be updated so they comply with our wishes (i.e. if we want either ENTER key OR some sort of Submit button OR ENTER key AND submit button to submit the interaction) - but until then, hopefully this will help someone.
47 Replies
Hi there Jennifer,
Thanks so much for reaching out about this issue, and our team is seeing the same thing. From what we can tell so far, the issue happens when the learner uses the Enter key immediately after typing their answer in a text entry field.
We know this bug is causing a snag for your learners, so our team is taking a closer look at what could be causing this. While I don't have an ETA to offer at this time, we'll be sure to keep you posted on any updates we receive.
Thank you! Oddly enough, I just found a workaround that seems to be ok. If I make the entry box larger to accommodate 3 lines or so, the enter key no longer takes away tabbing on the feedback layer. No idea why, but it's working!
Oh that's interesting! Thanks for sharing that tidbit. I'll do some more testing on that and add it to our bug report.
Thanks again, and I'm glad you got it working!
Can someone please provide an update. Has this issue been resolved?
Hi Stephanie,
There are a couple of conversations here, and with regards to the original question:
The Enter key will submit a Text Entry question type as you can see in this documentation.
I see that you are replying to Alyssa's last response, so perhaps you are running into the issue shared here about tabbing to the feedback layer. This is still open with our team and I do not have an update at this time. This conversation is attached so that we can provide an update here as well.
Hi Everyone,
I am reaching out to share that the issue where you can't tab to feedback layer items when using Enter to submit text entry interaction has been resolved!
The next step is to update Storyline 360 by heading to your Articulate 360 desktop app and clicking "Update" next to Storyline.
If the problem reappears, please let us know! We are happy to help!
Good Afternoon,
This issue is still happening for me and I have the most up to date version of Storyline. When users are typing and accidentally tap the enter button it submits the slide. I would like to prevent this from happening altogether. Please let me know if there is a workaround.
Thanks,
--Jes
Hello Jessica!
When there's a data-entry field on a question slide, pressing the Enter key on the keyboard submits the learner's response for evaluation. In other words, pressing the Enter key is the same as clicking the Submit button.
A workaround for this is to add a trigger to the submit button to determine when the user can "Submit Interaction".
Hello Jessica- this sounds promising. Do you have an example of a trigger?
could it be a check box under the text field? The user will have to check the box prior to submitting the response. How does it sound?
I am having this problem again three years later...
I have three text entry boxes on screen - I do not want the enter key to submit the answers..
HOW do I stop this happening??
Is there a quick way round it?
I have the latest version of storyline.
Hi Rebecca,
If you increase the height of the text entry box to be more than two lines, then the Enter key registers as a carriage return (new line) and does not submit the question.
Does that help with your setup?
Hi Ren,
I have tried making the text entry bigger, but that doesn't work. Enter still submits the question! I hope I solution can be found.
I am also having this issue. I've read that different questions types might be helpful. Is there any solution for this yet?
Hello Vanessa and welcome to E-Learning Heroes. 😊
When there's a data-entry field on a question slide, pressing the Enter key on the keyboard submits your response for evaluation. In other words, pressing the Enter key on the following question slides is the same as clicking the Submit button.
You can press Shift+Enter to add line breaks to short-answer surveys and ungraded freeform text-entry questions when the fields are tall enough to allow multiple lines of text.
Hi Annemarie,
Thanks for the additional information. Does Shift+Enter work for you?
Hi Leslie,
When I adjusted it to an essay question, the [enter] button could be pressed without submitting!
Thanks!
That's great, Annemarie. I appreciate you sharing the solution that worked best for your project.
Hi All, I have update my Storyline 360 to the latest version but I'm still having problem with the Enter key not getting the value user type on the text entry. I've set the submit button on the slide & Enter for submit keys. But it doesn't work, when user press Enter key, they're just advancing to next slide. When I want to show their typed value on the last slide, it doesn't show. Can someone help me?
Hi Atikah and welcome to E-Learning Heroes. 😊
We'd be happy to help you.
With your permission, I'd like to take a look at your project file to investigate what's happening. You can share it publicly here, or send it to me privately by uploading it here. I'll delete it when I'm done troubleshooting.
I'm running into a slightly different version of this problem. We present learners with a sentence that has no punctuation and ask them to type the whole sentence into the text entry field with correct punctuation. Some sentences are long enough to need two lines, so we make the text boxes tall enough for that. They are allowed 2 attempts. There is a custom submit button on the slide with a trigger to submit the interaction when user clicks submit button.
If learner enters text and presses submit, all is well.
However, if learner enters text and hits ENTER out of habit, that submits the interaction.
The problem is that the ENTER also registers as a linebreak so even if they enter the correct answer, the extra line break makes the answer register as incorrect. When they go back for their second attempt, the linebreak is still there and very easy to miss, so the learner can easily still get the incorrect feedback layer just because they have a linebreak at the end of their answer.
So we need Storyline to either interpret ENTER = submit or ENTER = text entry, but not both at the same time.
Hello Christina!
It sounds like you're looking for the option to choose whether the Enter key will allow a user to submit a question or add a line break. I'm happy to share this approach with my team.
Currently, when there's a data-entry field on a question slide, pressing the Enter key on the keyboard submits your response for evaluation. Using Shift+Enter will add line breaks. On a content slide, Enter or Shift+Enter adds a line break (return), so you can start a new paragraph.
I did find a workaround that to be honest, is a bit clunky but it does the trick. Here's a quick demo!
This post was removed by the author
To whomever still needs this functionality, I did find a workaround. Essay didn't work for me because we needed people to be able to see and print, if desired, what they entered and what the suggested responses are with the Review Result option. We hope people don't use the enter key, but we can't control what users decide to do.
I will say, it is a little annoying that we have options for how to submit in the quiz form - which is to use a button and (or at least it seem so) to submit with a keystroke. One would assume if that is blank, that a keystroke would be ignored.
That said, here's how I got this to work (you may need to modify it a bit based on your needs):
Note: I used a custom Submit button in the page, but this should work with the player submit button.
I did have some extra stuff to suppress the Next button and show the custom submit button until the slide was answered (so on review they can use the Next button) - so this shouldn't change anything - I just mention it in case...
Question type: Fill in the blank (I had a longer entry box)
Question properties: Feedback "By Question", Attempts Unlimited
Setup:
Create variable FIXEnterPressed (True/False)
Add a trigger - change FIXEnterPressed to FALSE when the timeline starts
On the Submit button (on click), add the triggers to adjust FIXEnterPressed to TRUE and then Submit interaction (order is important)
Delete the Correct and Incorrect feedback layers. Make the Try again layer blank (change the master and delete any 'artifacts' that may remain), set the timeline to the shortest time (we really only want it open for a very short time, just to run a trigger)
Adjust Try Again layer properties to: Hide other slide layers (or not, really shouldn't matter), Hide slide layer when timeline finishes, revisiting: Initial State, (others are deselected)
Add a trigger in Try again layer to jump to next slide when timeline starts if (condition) FIXEnterPressed is equal to True
---
So essentially what we're doing here is passing a variable to check when Submit is pressed vs when someone presses Enter. We have to hack it by using the Try Again layer, otherwise the question submits before anything else, so we can't really hijack the logic.
Ideally and hopefully the question properties will be updated so they comply with our wishes (i.e. if we want either ENTER key OR some sort of Submit button OR ENTER key AND submit button to submit the interaction) - but until then, hopefully this will help someone.
Best--L
This post was removed by the author