Text Entry fields not setting when control loses focus in mobile devices (Storyline 360)

Hi there Lu,

Thanks for sharing your findings here. I've heard of a similar issue in Storyline 2, but I haven't seen this reported for Storyline 360. I'm going to do some testing, and I'll come back when I have more information!

Hi Lu,

Thanks for your patience. I created a test file and uploaded it to SCORM Cloud for testing, and it seems to work as expected on mobile devices. Here's a link to the file for you to test, as well. I'm interested to see if your file is set up differently than mine. Are you able to share it here in the forums? 

Hi Alyssa, thank you for the follow-up. I did some research and created a scenario similar to the course we launched that has caused the mobile issues and tickets. It appears that it's the closing of the keyboard that sets the value. If a manual submit button is added (not on player) to the slide and triggered with variables and that button is clicked before closing the keyboard on the iPad, the value isn't set.

I loaded a 2 slide course into SCORM Cloud to show this. The first includes a text entry that is built with variables around the submit button (no quiz slide). If you click Submit before closing the keyboard, the value doesn't register. The second slide is one built with the convert to freeform text entry and uses a Submit button in the player. This slide works fine, likely because the keyboard has to be closed to access submit arrow.

https://cloud.scorm.com/sc/InvitationConfirmEmail?publicInvitationId=6577ce54-21c6-474d-8b0e-6fa06bafd52e

I assume this is expected functionality of the iPad. We can add a starter explanation slide to the course to explain the need to close the keyboard before submitting.

Thanks so much for your help.

Lu

Hi there Lu,

Thanks for setting up that demo - I can see that using a manual submit button doesn't set the value when the keyboard isn't closed. I'd like to pass this along to our Quality Assurance team for review. Would you mind sharing that sample .story file here?

I am having the same problem. I tried to fix it by using the Submit button on the player, but when I tested it on my iPad, the keyboard didn't cover the Submit button-- the entire player was pushed upwards so the Submit button was still visible above the keyboard. Do you know if there's any way to fix that? Would it be related to the player size settings?

Hm, that's interesting. I tried to recreate that behavior in a file, but I still need your help. Can you tell me a bit more about your set up?

• What version of Storyline are you using?
• What browser size and player size settings did you select?
• Did you publish the content for Web or LMS?

Hi Alyssa, I'm using Storyline 3. My browser size setting is "Resize browser to fill screen" and my player size setting is "Scale player to fill browser window." The content is published for LMS.

Ah, okay! Thanks for those details. I used those settings in the file linked here. Give that link a try on your mobile device, and let me know if you see the same behavior. 

Hmm... the link you sent worked fine. Do you think it could be a problem with the LMS I'm using?

Hi Adrienne,

Thanks for confirming. Since you're not seeing the same behavior in SCORM Cloud, I'd share that information with your LMS provider. Which LMS do you use? Hopefully other folks in the community who use the same LMS can offer some suggestions here.