We've identified that text entry fields that are added to a slide using Storyline 360 do not register if the user enters a value and then immediately clicks a Submit button when using a mobile device. In order to get the value to register, the user needs to click outside the text entry field before clicking the Submit button.
On a MAC or PC, the text entry value does register when the Submit button is clicked.
Does anyone know of any workarounds, other than to provide instructions at the start of the course?
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!
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.
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 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?
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.
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.
Did the QA team find a solution to this? I am having the same issue. The keyboard needs to be closed before hitting the submit button(on the slide not the player) or the control won't lose focus and set the typed variable.
What version of Storyline are you utilizing? It looks like we weren't able to re-create many of the issues listed above, so please feel free to share your .story file if you'd like us to take a look.
Thanks Lu. I apologize for any confusion. Looks like you are still subscribed to this thread, so you will see subsequent responses. I was reaching out to Charlie and I think you may have gotten that notification :)
I'm using Storyline 360. I uploaded the course through SCORM cloud. This issue was replicated on both an iPad 2 and an Android Galaxy s3. This issue occurs on mobile devices, not on a desktop computer.
My issue is exactly the same as described in the original post by Lu. In order to get the value to register for a text-entry, the user needs to tap outside the text entry field before tapping the Submit button. As described above, it seems that the device's keyboard has to be closed first, and the only way for the user to do that is to touch anywhere outside of the text-entry area.
You're exactly correct. It looks like the user has to close the mobile keyboard by tapping "Done" or tapping outside the text-entry area in order for the text entry value to be set.
Our team is reviewing this behavior, and you're in the right place to stay updated. We'll post any new information we get right here in this thread. Thanks for checking in!
Sorry to hear that this issue is affecting you as well, but thank you for chiming in to let us know. We are tracking user impact for this issue as this helps us prioritize.
This article is helpful in understanding how we tackle bugs.
I tested a bit more and it seems to be that text entry field does not get "lostfocus" rigth. For example i have slide with one text entry field and one button - and i put buttonclick event to check if text entry field is blank. So it should be that when i enter some text and then click the button .. the text entry should loose focus when i click button ... but it does not at first click. Next click on button does the trick. So bug i would say.
Please be sure that you are on the latest version of Storyline 360, then republish and retest your content. If you need us to take a look, please share the .story file for us to take a peek.
Hi,
Here is my sample story. Problem is with javascript excecution at "loose focus" event.
I´m building a validation of input ... so I would like to execute a javascript validation function as soon as the input field does loses focus.
But it seems that for some reason it is not working correctly - take a look at my sample. I put now only one-liner simple javascript to demonstrate the problem.
And this is not related to mobile as it has same problem in my PC.
84 Replies
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?
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.
Did the QA team find a solution to this? I am having the same issue. The keyboard needs to be closed before hitting the submit button(on the slide not the player) or the control won't lose focus and set the typed variable.
Hello Charlie!
What version of Storyline are you utilizing? It looks like we weren't able to re-create many of the issues listed above, so please feel free to share your .story file if you'd like us to take a look.
For me, it was Storyline 360. I have a course in a post above in which the issue was able to be reproduced by Alyssa.
Thanks Lu. I apologize for any confusion. Looks like you are still subscribed to this thread, so you will see subsequent responses. I was reaching out to Charlie and I think you may have gotten that notification :)
Yes, Leslie, thank you. I just wanted to make sure you had seen my experience with the issue.
Thanks Lu :)
I'm using Storyline 360. I uploaded the course through SCORM cloud. This issue was replicated on both an iPad 2 and an Android Galaxy s3. This issue occurs on mobile devices, not on a desktop computer.
My issue is exactly the same as described in the original post by Lu. In order to get the value to register for a text-entry, the user needs to tap outside the text entry field before tapping the Submit button. As described above, it seems that the device's keyboard has to be closed first, and the only way for the user to do that is to touch anywhere outside of the text-entry area.
Hi Charlie,
You're exactly correct. It looks like the user has to close the mobile keyboard by tapping "Done" or tapping outside the text-entry area in order for the text entry value to be set.
Our team is reviewing this behavior, and you're in the right place to stay updated. We'll post any new information we get right here in this thread. Thanks for checking in!
Any news here? We are having same problems with text entry fields.
Hello Timo and welcome to E-Learning Heroes :)
Sorry to hear that this issue is affecting you as well, but thank you for chiming in to let us know. We are tracking user impact for this issue as this helps us prioritize.
This article is helpful in understanding how we tackle bugs.
I tested a bit more and it seems to be that text entry field does not get "lostfocus" rigth. For example i have slide with one text entry field and one button - and i put buttonclick event to check if text entry field is blank. So it should be that when i enter some text and then click the button .. the text entry should loose focus when i click button ... but it does not at first click. Next click on button does the trick. So bug i would say.
Thanks for the additional information Timo. I'll add this to the report as well.
Actually Timo - upon further investigation to add your notes, it looks like this may have been corrected.
I have a brief file here that is now working.
Please be sure that you are on the latest version of Storyline 360, then republish and retest your content. If you need us to take a look, please share the .story file for us to take a peek.
Hi,
Here is my sample story. Problem is with javascript excecution at "loose focus" event.
I´m building a validation of input ... so I would like to execute a javascript validation function as soon as the input field does loses focus.
But it seems that for some reason it is not working correctly - take a look at my sample. I put now only one-liner simple javascript to demonstrate the problem.
And this is not related to mobile as it has same problem in my PC.
Hmm. attachment did not work from mail so here it is