The topic is quite popular in the forums. You might find some of the first few threads returned by the forum's search tool quite educational. I'd suggest "chrome font rendering preview"
Thanks for sharing the images here. The differences you're seeing in the Notes section are a bug we've reported to our team. It's specific to the HTML5 output and browsers such as Chrome have started to block Flash by default - so you're likely seeing the HTML5 output always.
I'll keep you posted on the status of this bug by sharing any updates here.
This might be related, I'm not sure. I'm finding that some of the feedback screens look different on Chrome than they do in Preview. Basically, in Chrome some of the feedback image is missing. I've attached two images to show you what I mean. The one titled "Feedback bug" is what I'm seeing on Chrome after I publish my file.
Here's a copy of the file. You need to Publish the file rather than preview it to see the issue. Go to slide 4 and try a MC question and choose answer A or C and you should see the issue.
Thanks Hedrink - I saw the same thing in your file. It seems to be connected to custom elements in feedback layers and happens in Chrome HTML5 output. I tested it as well in Firefox and Internet Explorer in HTML5 and both behave normally there.
I'll report the behavior with missing elements to my team as a possible software bug. From here, I’ll meet with my team to take a closer look so we can determine next steps. Sometimes my team catches errors in my logic and we don’t have a bug after all. Of course, if that’s the case, I’ll let you know!
Depending on priority and risk, some bugs can be fixed quickly, while others take longer to resolve. Here's more information on how we identify and tackle bugs.
I’ll let you know as soon as we have an update on this issue. Thanks so much again for letting us know about this, and I’m sorry if it’s slowing you down.
9 Replies
The topic is quite popular in the forums. You might find some of the first few threads returned by the forum's search tool quite educational. I'd suggest "chrome font rendering preview"
Hi Brian, I have started looking, but I haven't found anything recent. Someone mentioned the issue over 4 years ago.
Hi Jen,
Thanks for sharing the images here. The differences you're seeing in the Notes section are a bug we've reported to our team. It's specific to the HTML5 output and browsers such as Chrome have started to block Flash by default - so you're likely seeing the HTML5 output always.
I'll keep you posted on the status of this bug by sharing any updates here.
Thank you Ashley. I look forward to your update soon.
This might be related, I'm not sure. I'm finding that some of the feedback screens look different on Chrome than they do in Preview. Basically, in Chrome some of the feedback image is missing. I've attached two images to show you what I mean. The one titled "Feedback bug" is what I'm seeing on Chrome after I publish my file.
Thanks for the added information Hedrick.
Hi Hedrink,
Could we get a copy of that file to take a look? Or do you already have an open Support case with our team?
Here's a copy of the file. You need to Publish the file rather than preview it to see the issue. Go to slide 4 and try a MC question and choose answer A or C and you should see the issue.
Thanks Hedrink - I saw the same thing in your file. It seems to be connected to custom elements in feedback layers and happens in Chrome HTML5 output. I tested it as well in Firefox and Internet Explorer in HTML5 and both behave normally there.
I'll report the behavior with missing elements to my team as a possible software bug. From here, I’ll meet with my team to take a closer look so we can determine next steps. Sometimes my team catches errors in my logic and we don’t have a bug after all. Of course, if that’s the case, I’ll let you know!
Depending on priority and risk, some bugs can be fixed quickly, while others take longer to resolve. Here's more information on how we identify and tackle bugs.
I’ll let you know as soon as we have an update on this issue. Thanks so much again for letting us know about this, and I’m sorry if it’s slowing you down.
This discussion is closed. You can start a new discussion or contact Articulate Support.