Keypress functionality stops working when relaunching content on Scormcloud


Can anyone help please?

I have had a lot of fun creating a system simulation course which only uses keyboard interactions to move on.  Storyline 360 allows you to check for a key press, but I couldn't add validation because there is no trigger to check if you haven't selected the correct key.  You can change the slide to use the 'shortcut key question' type, but then you can't check for TAB or if the user has pressed a number (because the number pad and numbers on top of a keyboard are different).  

Anyway, we have written javascript to overcome all of this and it works. However, when the user stops the course or relaunches it from their LMS, the code no longer works.

On the first 2 slides of my course, it is just using basic keypress triggers and they also do not work.  

Has anyone else had similar issues with basic keypress triggers not working when you relaunch a course in an LMS?

I hope someone can help :-)

Thank you


13 Replies
Debs Churcher

Just following on from this.  I have created a clean Storyline file with 3 slides.  The first 2 slides have basic keypress triggers, which work fine when you first run it in Scormcloud.  When you relaunch it, they don't work.  The slides are set to reset to initial state when revisiting.  I have uploaded this course if anyone has any ideas.  This is a massive project that we are building in Storyline and I could really do with knowing if this is a known issue and whether there is anyway round it.

Thank you

Debs Churcher

Update on this - after much stress and headaches this is due to a bug in Storyline.  If the content resumes then the keyboard functionality no longer works no matter what SCORM you publish this as.  So basically, if your course has keypress simulation then you need to set the player to 'never resume' on start.  

Debs Churcher

I have logged a fault issue and on their initial investigations, they have confirmed that this is an issue.  Whilst they look into this further, they have advised that if you publish with the classic player instead of modern, it does work as expected.  This might help some people in the meantime!

Katie Riggio

Welcome ..and thanks for reaching out to the community, Debs!

I see you also opened a support case for the same issue–brilliant move! I took a peek at the case where my teammate, Robert, indeed logged the following behavior for our team to look into: the keypress trigger doesn't work when users resume the Modern Player. Looks like this behavior doesn't happen when using the classic player.

I've tagged this discussion, so we can keep you updated with any new information here, too!

Thanks for bringing it to our attention, and I'm very sorry for any headaches! 

Debs Churcher

Hello Patricio

There are 2 solutions to get round this issue:

  1. Publish the course as Classic player (the course will be a fixed size)
  2. Change the settings in Player so the course 'never resumes' (the user won't be able to return to where they exited the course if they close and exit midway through)

So you just need to decide whether scalable content or bookmarking is more important I am afraid, but at least there is a solution.

Debs :-)

Jason Kramer

I have been noticing this issue with the classic player. I have a number of key press triggers that seem to be randomly not working. I haven't been able to replicate the exact situation, but these have all been working for well over 6 months in multiple courses, and now they are randomly not working.

Ren Gomez

Hi Everyone,

Good news! We fixed the issue in Storyline 360 where the keypress trigger doesn't work when users resume using the Modern Player.

Here's how to install the latest Storyline 360 update to see all the recent enhancements and fixes.

If the problem reappears, please record a Peek 360 screencast for me, and I'll be happy to help!