Resize Browser to Optimal Size

In my custom players in Storyline, I've always checked the options to Resize browser to  optimal size, and to lock player at optimal size. This has always worked.

For some reason, for a current project, choosing these options has no effect. I am publishing for LMS and Tin Can. I've tested the modules on SCORMCloud and Litmos; on both systems, the course window is not fully visible, and both horizontal and vertical scroll bars display. (I've attached a screen shot showing what it looks like.)

I can't imagine what I may be doing differently. I've worked with Storyline now since it was first released, and have used these options exclusively.

8 Replies
Christie Pollick

Hi, Rebecca - 

Have you had a chance to take a look at this tutorial on Changing the Browser Settings and Player Size?

Also, there are a few things we can try to rule out some common issues. Please make sure you are working locally as described here, and you may want to try importing the file into a new file. If you are still having issues, you might want to try to repair Storyline. Also, could you please ensure that you are utilizing the most recent SL2 Update? Info on Update 5 can be found here

Christie Pollick

Hi, Rebecca - I was able to recreate the issue you are seeing. As you specified, I checked the options to Resize browser to  optimal size, and to lock player at optimal size. I then published a test file for SCORM 2004 and it resized accordingly, but when I published for Tin Can API, the scroll bars displayed for me as they had for you. I believe this may be a bug, and I am going to submit this issue for further investigation with our QA team. Although I cannot provide a workaround or a timeframe for resolution, I will be sure to update here in the forums with any information I receive. Thank you for bringing this to our attention.

Christie Pollick

Hi, Rebecca -- Thank you for touching base, but unfortunately, I do not have any updates from QA at this time. There were no changes related to the Tin Can output with the Update 5 release other than what is listed below:

  • Enhanced Tin Can API reporting for easier identification of tracked elements
  • Fixed issue where Tin Can API content wouldn't respect LMS-specific activity IDs

I will be sure to update here in the forums with any information I receive. Your patience is appreciated.