Key press triggers not working after an overlaying layer hides.

Jun 04, 2012

If you create a layer on a slide and create a method by which the layer is shown (I'm using a "mouse hovered over" trigger connected to a show layer action, with "restore on mouse leave" enabled), when that layer closes, any "key pressed" triggers on the underlying slide or layer will not function.

At this point, if you click anywhere on the slide the key press triggers will begin working again normally.

This leads me to believe that the layer that was previously showing still has 'focus' despite being hidden. This only seems to affect the key board triggers, because mouse click triggers obviously establish the correct focus and activate the right triggers to begin with.

Is this a bug? Is there a workaround or a way to force the underlying layer to 'grab' the focus? Is there something mystical and esoteric that I'm failing to account for?

61 Replies

Leslie McKerchie
Staff

almost 8 years ago06/20/16 at 5:59 pm (UTC)

Thanks for updating your response and uploading your file Beverley. I will take a look and respond back soon.

Leslie McKerchie
Staff

almost 8 years ago06/20/16 at 6:55 pm (UTC)

Hi Beverley!

Thanks for your patience and for allowing me to take a look at your demo file.

I was able to see the same behavior you are reporting here when I published your course and viewed on my iPad.

I tweaked the 'Submit' button that was displaying on the layer and simply hid it trying to sort out what was happening with this in the HTML5 output and it seems to have alleviated the issue.

Do you still have the issue in this published output on your iPad:

https://cloud.scorm.com/sc/InvitationConfirmEmail?publicInvitationId=81479002-3bc9-4260-bdf7-5605b8493ae9

Beverley Bowen

almost 8 years ago06/21/16 at 9:06 am (UTC)

That's great, it works, no more issues.

Thanks

Leslie McKerchie
Staff

almost 8 years ago06/21/16 at 1:34 pm (UTC)

Thanks for the update Beverley :)

Learning Agency og SES Team

almost 7 years ago06/12/17 at 8:59 am (UTC)

I am having the same issue in storyline 360. I have navigation via key pressed, left and right arrow. These does not work, untill i click the window with the mouse, which defeats the purpose. Any update on this old issue?

Alyssa Gomez
Staff

almost 7 years ago06/12/17 at 9:29 pm (UTC)

Hi Rasmus,

Can you tell me more about what you mean when you say you have to click the window? Do you mean you have to click the browser where the course is playing?

Do you have to do this for every slide, or just once?

Ali Goulet
Staff

almost 7 years ago06/12/17 at 9:29 pm (UTC)

Hey Rasmus!

I did a really quick test for this and did notice that in Preview for Storyline 360 you have to click the window before the key press will work to advance the slide as you're describing.

However, once I published the course and uploaded it to the web to test it- I didn't have to click before pressing the key to advance to the next slide. Take a look at it here and let me know if you have to click it first.

almost 7 years ago06/13/17 at 1:23 pm (UTC)

Hi Ali, thank you for the reply. In your example it works. I did a web publish of my course and uploaded it, which also worked. But the issue persist on the clients LMS. Could it be the LMS publish is doing something different than the HTML? Or maybe it depends on if its running flash or html?

almost 7 years ago06/13/17 at 1:23 pm (UTC)

Hi Alyssa, thank you for replying. On the clients LMS, i have to click inside the browser for each slide, before the key pressed works.

almost 7 years ago06/13/17 at 1:26 pm (UTC)

I also disable everything on the player. Menu, navigation and so on, so its just a white frame. Dont know it that makes a difference.

Ali Goulet
Staff

almost 7 years ago06/13/17 at 2:29 pm (UTC)

That's great information to have, Rasmus. Definitely a bit strange that it works on the web but not in the LMS. Thanks for letting me know that.

Would you be able to share the .story file you're working on with me so I can do some more testing? You can add it as an attachment in the thread like this: