Layer disappears when running on iPad in Safari (works fine on PC)

Jun 04, 2013

Sean Bernardino
By Sean Bernardino

Hi, 

For one of my courses, I've created a layer which basically acts as the closed captioning layer for the slide. This layer toggles in Show/Hide mode depending on the toggle button that I've created. While this runs fine in the PC version of the published output, when I view the same output on the iPad (in Safari mobile browser, as our client would does not want this to be run in the Articulate mobile player), the closed captioning layer automatically disappears after the first few seconds on each slide. I've looked everywhere to see if there's a trigger toggling the view -- but there isn't. In fact, the CC layer continues to be displayed (when in Show mode) when I view this on the PC, but for some reason it vanishes from the iPad.

Would appreciate any help I can get on this.

Thanks,

Sean Bernardino

11 Replies
Christine Hendrickson
almost 11 years ago06/04/13 at 8:55 am (UTC)

Hi Sean,

Can you tell me what version of Storyline you're using, please? To find this information, click on "Help" and "About Articulate Storyline".

If you're not running version 3 (1305.2012), please download and install the update using the link below:

Articulate - Storyline Update 3

Once you've finished installing the update, please republish and test your course on the iPad. If the problem continues after installing the update, or if you already have Update 3 installed, please let me know.

Thanks very much!

Christine

Christine Hendrickson
almost 11 years ago06/05/13 at 6:44 am (UTC)

Hi Sean,

Thanks for confirming that :)

You might want to check out the following article just to make sure you're not using any effects or features that aren't supported in HTML5:

Comparing Storyline's Flash, HTML5, and Articulate Mobile Player output

I know you mentioned the client doesn't want this project distributed through the Articulate Mobile Player, but have you had a chance to try publishing with this method? It would help narrow down the issue, if you could try this just for testing.

If caption layers are still closing, are you able to share the .STORY file here, or send it to us privately? 

Thanks Sean!

Christine

Christine Hendrickson
almost 11 years ago06/10/13 at 8:21 am (UTC)

Hi Sean,

I hope you had a great weekend!

I was able to find your case this morning (#00338001 for my reference). Looks like Sid has been working with you. 

I do see that Sid has sent out a couple of messages so far and I just wanted to make sure you've received them. If you haven't, please try checking your spam folder or filters. You may also want to add support@articulate.com to your safe senders list. If you still cannot find the message, just let me know and I'll try to send them out again. 

If you have received the messages and the last suggestions from Sid didn't resolve the problem, please respond so he can continue working with you.

Thanks very much!

Christine

Leslie McKerchie
over 10 years ago07/24/13 at 5:54 am (UTC)

Hi Jason! The issue that we are seeing is related to HTML5.  The workaround advised in the case mentioned above in this thread is to create the closed-captioning objects as states instead of layers while QA investigates the issue. I don't know the particulars of your issue to know if that previous advice will help you or not.  Just follow up if need be.  Thanks so much and have a great day!

Jason Johnson
over 10 years ago07/24/13 at 4:49 pm (UTC)

I like SL, don't get me wrong....BUT there are WAY too many issues with this tool in terms of HTML5 output. Layers should amount to a div tag in HTML5 that is shown/hidden and there should never be a reason why div content is problematic for show/hide functionality which is all we're talking about there. I should be able to put anything I want in a div and have it appear as expected with little issue. So frustrating...

It seems like every other post I read or put up myself results in a member of SL staff asking me if I want to open a tech support ticket or submit a feature request because it's something SL can't do presently. Again, frustrating!

Sign In to Reply