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?
Strange. Your output version works ok also here. But here i still have problems with my output - and I´m running latest version of Storyline360. I need to test more and see what could be the reason. Does it work for you locally (just publish and run locally)?
When you view a Storyline 360 course on your local hard drive, you'll encounter security restrictions from the computer, web browser, Flash Player, and network that can cause various features of the course to fail. To test your published content and share it with others, it's best to upload it to a web server or LMS. See this article for details.
The original issue reported here was for the text entry fields not registering or setting the value when the user hit Submit on a mobile device prior to closing the keyboard. Is this what you are seeing as well?
Please be sure that you are on the latest version of Storyline 360, which is now Update 13, as we show this was corrected in Update 8.
If this is not what you are experiencing, please share the details and your .story file if possible.
I'm having this same issue as well where you have to close the browser to get the variable to set on an android device.
Clicking elsewhere or even on my Next button (which has a trigger to not go forward unless a number has been entered) won't be enough to make it "lose focus" and set the variable.
I have a ticket in for this and other reasons but I just wanted to chime in to see if the issue was still being worked on and let others know they're not alone!
Add an Execute JavaScript trigger to your Submit button (before all other Submit button triggers fire) and run the following JS:
document.activeElement.blur();
This will remove the focus from the active text entry field (closing the mobile keyboard) and therefore commit the text entry to the associated variable prior to the Submit button assessing correct/incorrect.
84 Replies
Hello Timo!
Do you experience an issue with my published output here? Your alert window pops up for me which is what it looks like you set up in the course.
Strange. Your output version works ok also here. But here i still have problems with my output - and I´m running latest version of Storyline360. I need to test more and see what could be the reason. Does it work for you locally (just publish and run locally)?
Hello Timo! I do not test the content that way.
When you view a Storyline 360 course on your local hard drive, you'll encounter security restrictions from the computer, web browser, Flash Player, and network that can cause various features of the course to fail. To test your published content and share it with others, it's best to upload it to a web server or LMS. See this article for details.
Same problem here with at least some of my content.
Hello Robert!
Sorry to hear that you're running into an issue with this. What version of Storyline are you using?
same problem.. ipad/android not performing "set textentry equal to typed value" when control loses focus
Hi Sebastjan,
Sorry to hear that you've run into a similar issue.
We show that this issue was corrected in Update 8 for Storyline 360.
Are you using the latest version, which is now Update 13?
If you need us to take a look, please share a sample .story file.
Gladly. Where can I share file privately?
Sorry about that :)
You are welcome to share privately here.
tnx.. Case Number: 01291937
Thanks Sebastjan!
any update?
update from my side - this error is not present in SL2 export.. seems to be 360 "feature"
360
Thanks for the update Sebastjan.
I took a peek at your support case and it looks like Renato has filed this as a possible bug.
I wanted to share some information on how we define bugs and how we tackle them when they occur.
I'll attach this thread as well so that we can post an update here when we can as well.
Thanks for confirming Robert.
The original issue reported here was for the text entry fields not registering or setting the value when the user hit Submit on a mobile device prior to closing the keyboard. Is this what you are seeing as well?
Please be sure that you are on the latest version of Storyline 360, which is now Update 13, as we show this was corrected in Update 8.
If this is not what you are experiencing, please share the details and your .story file if possible.
Yes, this is the same bug that we are experiencing. I'll double check to see which version of Storyline 360 was used to publish the file.
I can also confirm this, somewhat annoying and frustrating.
Hope you guys can fix it soon! :)
Thanks Robert :)
Hi Nejc,
What version of Storyline are you using?
As I mentioned above, we show that this was corrected in a previous update, so if you're still seeing it, we would certainly want to take a look.
I'm having this same issue as well where you have to close the browser to get the variable to set on an android device.
Clicking elsewhere or even on my Next button (which has a trigger to not go forward unless a number has been entered) won't be enough to make it "lose focus" and set the variable.
I have a ticket in for this and other reasons but I just wanted to chime in to see if the issue was still being worked on and let others know they're not alone!
Thanks for chiming in to share Alex and for letting us know that you've reached out to the support team as well.
I see that Eloisa is helping you out :)
Hi All,
I have a work around for the issue above.
Add an Execute JavaScript trigger to your Submit button (before all other Submit button triggers fire) and run the following JS:
document.activeElement.blur();
This will remove the focus from the active text entry field (closing the mobile keyboard) and therefore commit the text entry to the associated variable prior to the Submit button assessing correct/incorrect.
Im also experiencing the same issue using SL 360. Never had this problem before.
Unfortuantely JS doesnt work :(
Thanks!