Storyline 2 Update 10 HTML5 output issue in KC pages

Hi Kailas!

I do see where something similar was reported to our QA Team to review. Would you be able to share your .story file here so that we can take a look?

In an HTML5 output, only 1 option gets missing and that too randomly (Whether it is 2 options KC or 4 options KC) from every KC pages in storyline 2 update 10.

Yes, that sounds like what is being reported Kailas. It would be great if you could share your .story file via the link I shared above.

Hi Leslie,

Thanks a lot for your quick help.

I have uploaded the affected .story file on the above given link.

Thanks for the update Kailas. I see your case has been submitted (00908115) and you should be hearing from someone soon. I will follow along as well.

Yes... Thanks Leslie, I am getting email updates as well.

I am also trying to sort it out at my end, lets see if we can come up with a solution.

Sounds great Kailas. I see where Miker has reached out and is testing. I'll continue to follow along.

Great!

I have an update regarding what I was trying for!

while experimenting with the affected .story file I noticed that "fade in" effects works well with HTML5 output because, earlier there was "fly in" effect for the KC options I just changed it to "fade in" effect and surprisingly it worked. I even took fresh new .story file to be more sure and played with these 2 effects. Even in fresh new .story file the "fly in" effect doesn't worked with HTML5 output. "fade in" effect working correctly.

*KC options disappears with "fly in" effect for HTML5 output in SL2 update 10. This is what I have got concluded.

Please try this at your end as well and let me know your thoughts.

Hi Kailas! 

I shared your response in your support case for Miker.

Great!

Thanks Leslie.

Hi Leslie,

Got an update from Miker he is done with his analysis. He analysed the affected .story file in SL2 update 11 but, the issue I am facing is in update 10. Earlier I started working with update 11 but faced bolded font issue with published output. I wasn't able to view bolded words in published output. Just want to confirm that is there any such issue with SL2 update 11?

Hi Kailas! I have not seen an issue, but I see where you shared the details with Miker as well, so I'd await the result of his testing based on your scenario/file. 

Yes Leslie, I am in touch with Miker as well.

Thanks for the update Kailas :) I'll continue to follow along.

I popped in to check on your case Kailas - how is the testing going with another font?

Hi Leslie,

Due to project work I wasn't able to update SL2 update 10 to the update 11. Today I will update you on this.

Hi Leslie,

I have got the test result of fonts. There is an issue with "Avenir LT Std 65" font family, it doesn't support bolded font in SL2 update 11, while "Arial" font is working fine in this version.

I have submitted the test file to Miker. Hope he will sort it out soon. :) 

Thanks so much for the update Kailas and for continuing to work with Miker.