How to disable "Hit Enter Key to Advance Slide "

We don't want students to advance to next one before they view the whole slide. So we hide the next button until the end of the slide.

But we noticed that at the beginning of the slide, you can skip it by hitting enter key.

This is something like a "backdoor" to complete a course without even viewing the content. Is this a designed feature or bug?

Please let me know how to solve this.



17 Replies
Leslie McKerchie

Hi Philippe,

This is an issue that we have reported to our team.

I will add this conversation to the report as we continue investigating and so that we can update you here when we can.

We do have a workaround listed:

  • Delete the trigger that hides the Next button when timeline starts.
  • Restrict the navigation so that the Next button will be in its disabled state.
  • Use a trigger that would make the Next button Normal when timeline reaches x seconds.
Michael Johnson

Hello Leslie,

I was experiencing the same issue. I have a text box for the user to enter the information required. There is also a timer on these slides. The user should be able to advance before the timer runs out, but only if they have submitted an answer. However, the way I have it set up now if the user hits ENTER, they are able to advance without putting an answer. 

Ciara Nicole

Hi! I am replying on this thread, as I think someone here may be able to help me. I am trying to disable the enter key from advancing to the next slide, on a slide that I have a text entry box in - the question requires multiple answers, which I want the user to be able to separate by line breaks

(ex: MRI

Cat Scan

Brain Biopsy)

However, when you hit the enter key, it automatically advances to the next slide. I have no triggers set up for this, it is just automatically doing it. How do I disable this from happening? 

I am attaching the project, it is specifically slide 1.6 and 1.10



Leslie McKerchie

Hello Ciara 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.

  • 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.

Essay questions behave differently than other question slides since they're likely to have multiple paragraphs. You can press Enter or Shift+Enter to add a line break (return) in essays.

Maria Costa-Stienstra

Hi, Kent, and welcome to E-Learning Heroes! ✨

Thank you for reaching out! 

It sounds like restricting the navigation would work for you:

  1. Go to the Home tab on the Storyline ribbon and click Player.
  2. Click Menu on the player properties ribbon, then click the gear icon at the bottom of the window for additional menu options.
  3. Use the Navigation Restrictions drop-down list to choose Restricted.
    • Restricted means learners can view the current slide and any slide they previously viewed, but they can't jump ahead or skip over slides.
  4. Mark the box to Restrict Next/Previous buttons. (It's marked by default.)
  5. Click OK twice to close the menu options and the player properties.

Let me know if this works!

Diarmaid Collins

Hi Connie. Has there been any resolution to your issue?

Hi @Lauren. I am using Storyline 360 (Build 3.61.27106.0) and I have a number of text entry slides, some with single-line entries and others with 'essay' type entries. Pressing ENTER on the single entry fields records the user's input and progresses to the next slide - all good and as intended.

Pressing ENTER in the essay question simply jumps to the next slide and DOES NOT record the user's input. This is not good.

I have a dedicated (bespoke) SUBMIT button that the user should click and everything behaves as it should, but old habits die hard and some users are frustrated that when they hit ENTER their lengthy responses vanish into the ether.

I also have the ENTER button marked in the Submit Keys option, so I kind of don't understand why there are 2 separate behaviours for one button dependent on the size of the text field.

Why doesn't Storyline behave like it should?

Here's a demo in Review.