Buttons disappear if the video is in fullscreen

May 25, 2023

Kevin Gruppe
By Kevin Gruppe

Hey there,

I'm facing some issues with Storyline and I'd like to ask for your guidance on best practices. In my course, I have custom "Continue" and "Back" buttons. These buttons work fine when the video is playing, but if the user switches to full-screen mode, the custom elements like buttons disappear. From a usability perspective, I would like the buttons to remain visible even in full-screen mode.

As an experiment, I added a custom "Fullscreen" button with the following trigger:

Set Player.FullScreenMode = True when the user clicks on btn_fullscreen.

The trigger works as intended (as shown in custom.png).

Do you have any suggestions on how I can modify my trigger to work with the default fullscreen button? I haven't been able to find a solution yet.

Alternatively, could this be a bug in the software?

 

Thank you in advance and best regards,
Kevin

5 Replies
Jürgen Schoenemeyer
12 months ago05/25/23 at 11:57 am (UTC)

if you use the fullscreen button on the video navigation - this is the intended behaviour (video is fullscreen, no other elements)

only with the second fullscreen button from the modern player (or the javascript trigger) you can start fullscreen of the whole course with your buttons

https://360.articulate.com/review/content/be3979b5-bf33-429e-8893-af8b9b5cc039/review

 

Kevin Gruppe
12 months ago05/25/23 at 7:20 pm (UTC)

Thank you, Jürgen! We have made the decision to conceal the player and incorporate our own buttons to align with our company's design.

 

However, if someone reads this thread in the future, I have given some thought to this issue and discovered a simple solution:

  1. Place a Hotbox around the full-screen icon.
  2. Add a trigger that sets Player.Fullscreen to true when the user clicks the hotbox, only if Player.Fullscreen is currently false.
  3. Add a trigger that sets Player.Fullscreen to false when the user clicks the hotbox, only if Player.Fullscreen is currently true.

With these steps implemented, the case is now closed. :)

Best regards,

Kevin

Sign In to Reply