Storyline Text Rendering Problem on Published Course?
Jul 17, 2018
Whenever I hover over a button on Google Chrome, the text inside of the button slightly moves by a pixel or two (this is the basic button element on Storyline and is not a custom button). I have checked the states and it all has the same line height so that shouldn't be the cause.
Other necessary details about the published course that might help:
- The player resizes to fill the screen
- It works fine on other browsers except for Google Chrome
- The course is set to be published as HTML5 first with a Flash fallback
I am thinking this might be a problem on Storyline's end where the output is not properly anti-aliased or something is causing Chrome to not render the text properly. Is there a way that I could fix this or is this a bug on Storyline itself?
Unfortunately I also won't be able to share the storyline file as it's against policy however I attached a GIF that properly demonstrates the problem.
4 Replies
Hey Chris,
Thanks for sending over that GIF file! I'm going to try and recreate this in a new Storyline project, and I'll need a little more help from you.
Hey Alyssa!
I am on Storyline 3. My build version is Update 4: 3.4.15731.0 (have also clicked on Check for Updates just in case and it says I am on the latest one)
Yes, but unfortunately I am not allowed to share it.
I am also running the latest version of Chrome which is Version 67.0.3396.99
If you have any more questions, please let me know!
Hey Alyssa,
The issue should now be solved through a lengthy workaround, here's what I did:
- The slide (containing the buttons) had to be totally recreated on a new file from scratch
- The recreated slide then had to be imported to the original file
- After publishing, the issue was still occuring. I then tried to republish it.
- It was fine after republishing the main/original file with the recreated slide. Something went wrong on the software somehow during publishing the course.
I'm all good now and hopefully this workaround helps someone else in the future. Also can you please still look into it just in case it's a bug on Storyline itself? So this workaround doesn't have to be done in the future anymore.
Hey there Chris!
Thanks so much for letting me know how you solved it. I went through some testing, but I wasn't able to recreate the issue you described. It sounds like it was file-specific. In any case, I'm happy you were able to work around it!
If you run into this problem again, be sure to give us a head's up.
This discussion is closed. You can start a new discussion or contact Articulate Support.