Text entry bug in latest update

Mar 13, 2020

Hi all.

I discovered a bug in Storyline 360 today, which has been reported. If you have a text entry field it will stay 'on top' of any layers you have on that slide (including master slides).

For example, if you have a text entry field on the base layer and a popup window as a layer, when you open the popup window the text entry field will be on top of the layer. Here's a link to a Peek video to demonstrate what I mean:

https://360.articulate.com/review/content/df1b62c5-b4da-4d0f-898d-56c9d98d9731/review

This has been reported as a bug, so hopefully there'll be a fix for it soon. In the meantime there's a workaround of preventing the user from clicking on the base layer, although this isn't always preferable.

UPDATE: This appears to be another bug with a recent update, as modules we designed in a previous version of Storyline aren't affected by it.

49 Replies
MarkAnthony Chesner
MarkAnthony Chesner

Didn't work. Just thought, what the hell, let's paste it on the second layer that only showed a plain text, I had already tried maybe a hundred variations, mutations, zombifications, but in the end, walla!!!!

Don't know why, maybe because the layers are considered and separate pages overlapping and this clears the previous, bottom page, as viewed...I really have no idea, but it works!

Thank you Daniel!!!!

Daniel Holland

Yes, this should work...just change the text in quotes to what you need...now if you have more than one input this may not work and you  may have to target a specific input as of right now this works on all inputs.

var els = document.getElementsByTagName('input');

for (var i=0; i < els.length; i++) {

els[i].value=" ";

els[i].setAttribute("onfocus", "this.value=' ' ");

els[i].setAttribute("placeholder", "this.value=' Your text here ' ");

els[i].setAttribute("autocomplete", "off");

}

MarkAnthony Chesner

After some experimentation, I discovered that when the name fields are filled by Google Autofill, it wants to autofill all of the text boxes in the project...

Is there really no way to turn Google Autofill off from within the player???

Is there any way to name the elements so Google will not want to autofill? I tried naming the name boxes red, blue and green but with no change...

UPDATE: I was surfing around and found the chrome-off and it seems to stop the chrome autofill, but not the answers from previous attempts. But I does not break the rest of the input boxes on other slides, so 50% win....

var els = document.getElementsByTagName('input');
for (var i=0; i < els.length; i++) {
els[i].value="";
els[i].setAttribute("onfocus", "this.value='' ");
els[i].setAttribute("autocomplete", "chrome-off");
}

Penny LaLiberte

This is my first attempt at creating simulation using SME-provided screenshots that require text entry, and I’m having problems with text entry boxes on layers. I'm not sure if it has to do with the Storyline bug, but maybe someone can help.

Expectation:

  • Learner must enter the correct data in a designated field and then click outside of the text entry field to proceed.
  • On the base layer, if input is wrong or learner clicks outside of the text field, the yellow Try Again layer displays.
  • The Try Again layer has its own text entry variable. If input is wrong or learner clicks outside of the text entry field on the yellow Try Again layer, the red Incorrect layer displays.
  • The Incorrect layer has its own text entry variable. Learner cannot exit the slide until the correct data is entered and they click outside of the text entry field.

Reality:

If the learner gets the Base and Try Again layers wrong (by either clicking outside of the Text Entry field or entering the incorrect data), it goes to the Incorrect layer, which it is supposed to do. However, when you click the text entry field on the Incorrect layer (which is a separate variable for each layer), it returns to the Try It layer. The expectation is that It should stay on the Incorrect layer until the correct answer is entered and the user clicks off the field.

Would someone please help figure out what I’m doing wrong? A file showing my triggers/conditions is attached (5_text fields within layers.story) – note that these are just a few selected slides to give an idea of what’s occurring. I've also attached a narrated .mp4 explaining the issue.

Many thanks!

Ren Gomez

Hi Everyone,

Good news! We fixed the issue where the text entry field on the slide layer could be clicked, edited, and remains active in the base layer.

Here's how to install the latest Storyline 360 update to see all the recent enhancements and fixes.

If the problem reappears, please connect with our team, or share a screen recording here, and we'll be happy to help!

Astutis 2

Hi.

I've noticed that this bug still exists if you copy and paste a text entry box. If you add a new text entry box it's okay, but once you copy and paste it, the copied one still has the error. And once a copied text entry box has been created, it seems to completely break that slide, so even if you delete it and create a new one, the bug still exists. To get around it you need to completely recreate the slide from scratch and create a new text entry box every time. 

In our case this is extremely time consuming as we have around 10-20 text entry boxes in each of our projects, so it's going to take a considerable amount of time to recreate all these slides from scratch without being able to copy and paste anything. 

Please look into this bug.

Eric Santos

Hi Astutis,

I'm happy to help troubleshoot this issue and would like to start with clarifying questions to understand your experience better.

  1. Are you seeing the same bug reported in this thread where the text entry field on the slide layer could be clicked, edited, and remains active in the base layer? I ran some tests using the latest version in a sample Storyline project, and the error didn't happen. I also tried copying and pasting the text entry object with the same results. You can find the sample file I used attached below. TextEntry1 has been copied and pasted from TextEntry.
  2. If you see a different behavior, could you send a screen recording so we can understand what's happening?
  3. Does it happen to all your Storyline projects or only to a specific one? If it happens to all, try running these steps to fix possible installation issues.
  4. If it is file-specific, we'd be happy to take a look! Would you be willing to share a copy of your Storyline file here or privately through a support case? We'll delete it when we're done testing.

I appreciate your patience!