Issue with Increasing Player Font Size

Jul 14, 2017

Hi all: 

I increased the font size of my player text, but doing so seems to have created an alignment issue. I really only wanted to increase the size of the Menu tab since it's so much smaller than the navigation button text. Now the tab text goes off the player and icons in the scrollbar are completely out of alignment.

Is there better solution for this? Screenshot below. 

8 Replies
Leslie McKerchie

Thanks for sharing Amanda. The file looks pretty consistent to me. Looks like you were publishing for the web, so I published with the settings that you'd set and uploaded to Tempshare to take a look. Click here to see published output.

I did notice that you were viewing the published content locally, which is not a supported environment.

You mentioned LMS as well, so I also published for LMS and tested in SCORM Cloud which you can see here.

Let me know if you experience an issue with either of my published outputs and what environment/browser it happens in. 

My eyes may not be the best and it seems to match what I see in preview. We do, however, have a similar issue reported to our team related to this and I will add this thread for user impact.

Amanda Allen

Leslie: I played around with my browser settings and the issue seems to stem from my Font size settings in my browser. Once I reduced the font size to the default Medium, the issue with the project file resolved. The tab, however, is aligned to the very top of the player. It would be nice if the alignment was adjusted a bit to give a little space between the tab button and the player border. 

Leslie McKerchie

Hey Amanda,

Good news! We fixed the issue you reported where the player menu tab was cropped when the player font size was set to 200% when viewing the HTML5 output.

Install the latest Storyline 360 update to take advantage of all the recent features and fixes. Here's how.

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

This discussion is closed. You can start a new discussion or contact Articulate Support.