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?

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.

Hello folks, We are currently experiencing a similar issue as the original post of this thread. The Issue on Mobile Devices:By default in the latest Storyline program when you create a Text input box it automatically creates and assigns a variable and registers its value when the object loses focus. When you use a text entry object in Articulate Storyline, the text you type in the field does not get registered until the field loses focus. That means you need to click outside the field (for example, on a button) to make the the text entry field losing its focus. We are reading mixed messages in forums of some users blaming the Keyboard after iOS13,and others are saying it is a bug with Storyline that has not been resolved. We know for a fact this issue was not present in the June 19, 2018 (Build 3.17.16117.0) because we had our courses QC and iPad issues were not there. We are currently using V 3.38.24 as of 21-4-12. Our main issue now is the Mobile keyboard is always active, when you tap outside the field we can't get the Save+next button to lose focus. We are testing on iPad using the latest iOS. This does not happen on Desktop. Solution: We currently have a solution that involves JavaScript. What we do is add one extra line after publishing the files (We already reference to JQuery in our index lms) <script src="/client/name/businessPlan/js/jquery-3.2.1.min.js"></script> It’s using JavaScript and jQuery (therefore, it won’t work in the mobile app AMP). It only works on HTML5 JS Code will be placed in your Master slide/Your theme slide, it will not effect anything else: var p = GetPlayer(); var placeHolderText;$(":input").each(function() {var place = $(this).attr('placeholder');if (place !== undefined){ placeHolderText = place.split("|"); if (placeHolderText.length==2){ $(this).data('bd_place',placeHolderText[0]); $(this).attr('placeholder',placeHolderText[1]); $(this).bind('input propertychange', function() {p.SetVar($(this).data("bd_place"),$(this).val());});}} }); This also helps you to monitor what the user is typing letter by letter. This is the screen inside Storyline. It has the intro text. The text entry field. The placeholder text inside the field is important. Normally, it’s just what you want the user to see as a hint. This time, it contains two pieces of information, divided by “|”. The first part is the name of the Storyline variable (in this case, answer), the second is the actual text you want to display for the user. answer|[Type your text here] or answer|[Escriba su texto aquí] The program will remove the Storyline variable name in our case "answer", so the user won’t see it. However, when the user types in the field, the program will update this variable instantly. 2nd solution not tested: Execute JavaScript trigger to run at timeline start: $(function() {$("input").keyup(function() {$(this).blur();$(this).focus();});}); Basically it causes the active input element to lose focus very briefly after every keystroke, thereby activating the "control loses focus" trigger, to which you can attach any action you like on a case-by-case basis. Resources: https://community.articulate.com/discussions/articulate-storyline/entry-text-without-losing-focus https://www.rabbitoreg.com/2018/04/22/articulate-storyline-text-entry-without-losing-focus/

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

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

84 Replies

LeslieMcKerchie
Staff
8 years ago
Sorry about that :)

You are welcome to share privately here.
sebastjanf
Community Member
8 years ago
tnx.. Case Number: 01291937
LeslieMcKerchie
Staff
8 years ago
Thanks Sebastjan!
sebastjanf
Community Member
8 years ago
any update?
sebastjanf
Community Member
8 years ago
update from my side - this error is not present in SL2 export.. seems to be 360 "feature"
- LeslieMcKerchie
  Staff
  8 years ago
  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.
RobertKankelbor
Community Member
8 years ago
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.
- LeslieMcKerchie
  Staff
  8 years ago
  Thanks Robert :)
NejcZD
Community Member
8 years ago
I can also confirm this, somewhat annoying and frustrating.

Hope you guys can fix it soon! :)
- LeslieMcKerchie
  Staff
  8 years ago
  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.
AlexHunt
Community Member
8 years ago
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!
LeslieMcKerchie
Staff
8 years ago
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 :)
MatthewJevons-6
Community Member
8 years ago
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.
- StephanieSam195
  Community Member
  8 years ago
  Im also experiencing the same issue using SL 360. Never had this problem before.
  
  Unfortuantely JS doesnt work :(
- ThomasBleije661
  Community Member
  8 years ago
  Thanks!
- aaronkapala-97b
  Community Member
  7 years ago
  Hi All,
  
  This still seems to be an ongoing issues, I am on a trial version of Storyline 360 as we use Storyline 3 and there is an issue with Text Entry boxes not working correctly on mobile devices so this was the only way I could get my product out for testing at the time.
  
  I have been pulling my hair out trying to get them to record correctly without closing down the Keyboard and using the JavaScript line Matthew has mentioned has done the job - so thank you for your post, this has really saved us.
  
  Hopefully this could be sorted soon but also hopefully the updates in Storyline 360 can be replicated in SL3 so that the text entry boxes work correctly on mobile devices.
  - Crystal-Horn
    Staff
    7 years ago
    Thanks for checking in, Aaron. We have this issue open, and we've updated our notes with this information:
    
    On a mobile device, clicking submit directly after entering the text or numeric entry is not allowing the focus to change from the entry field. When the focus doesn't change, the trigger to adjust the entry variable doesn't fire, and the question is evaluated incorrectly.
    
    We are still looking at this behavior, and we'll let you know here about any changes that are released!

Forum Discussion

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

84 Replies

Related Content

Accessible Video Controls in Storyline

Customize the Player Settings in Storyline

Setting Your Slide Size in Storyline

Customizing the Theme and Course Settings

Storyline 360: Setting Storyline Options

Learn

Connect

Discover

Community

Company

Trust Center