Forum Discussion
Text entry bug in latest update
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.
- RenGomezStaff
Hi Shane,
Great question! I would connect with a support engineer to confirm which bug you're running into, as they can better provide details on what version may be a good one to rollback to, especially if it's a version you no longer see in the desktop app menu!
- ShaneLeonardCommunity Member
Gee thanks Ren.
To the folks that are impacted by this bug, after a few trial rollbacks, I can confirm that if you rollback to Version# 3.38.21861.0 released on April 7, 2020, then the bug no longer occurs and text input fields on layers (including red lines to indicate spelling mistakes) hide when the layer is hidden.
I hope this info is passed onto the team that actually actions bug fixes (if they actually exist) as it may help them identify the cause of the bug and resolve. - DanielHollandCommunity Member
I am experiencing the same issue. I have reservations about rolling back as I don't want that to affect anything else
Hi there, Daniel!
I respect your decision and will keep you posted on our progress with both bugs.
For now, we're happy to explore your file for any tailored options. As always, you can connect with our Support team through this case link.
- DanielHollandCommunity Member
I was able to workaround this with some javascript.
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", "off");
}
Not the most ideal, but it works- MarkAnthonyChesCommunity Member
Hello Daniel,
I am having the same problem. Could you tell me where you placed your script? And it seems that "input" would be the variable name attached to the text entry field if I imagine correctly....?
Thanks in advance!
- RussellBrown2Community Member
We have just encountered this exact bug using the latest version of Storyline 3 (Update 10: 3.10.22406.0). However, it appears to only impact some users in Chrome. And it doesn't appear to be specific to the Chrome version. 2 users with the exact same version of Chrome - 1 sees text entry fields on other layers after the layer closes, another doesn't.
In the screenshot, you can see that after you've entered the address (1 Island Dr) and the city (Oaks), then click the dropdown to select a state, you can see the text entry fields on top of the dropdown layer.
Hi Manuel and Shane!
Great news! We just released another update for Articulate 360 and included a few important fixes that you'll see in the release notes here.
The item you'll be interested in is:
Fixed: Scroll bars and red spell-check lines on one layer were visible on other layers when they should've been hidden.
Just launch the Articulate 360 desktop app on your computer and click the Update button for Storyline 360. Details here.
Please let us know if you have any questions, either here or by reaching out to our Support Engineers directly.- ChristaBauerCommunity Member
Hi there! Are you seeing this in Storyline 3 as well? We have a series of courses that have some slides that are the same with text entry. If they use the suggested text, it will stay on screen.
- DanielHollandCommunity Member
The JavaScript needs to be placed on any slide with a text input field. You just use an executed JavaScript trigger when timeline starts and copy and paste the JavaScript. Hope this helps
- MarkAnthonyChesCommunity Member
Thanks, Daniel!
Could you please doublecheck the code...it's not working for me, sorry...
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", "off");
} - MarkAnthonyChesCommunity Member
Thank you Daniel,
I am running different JavaScript in the project. You can find the project
in this thread:
https://community.articulate.com/discussions/building-better-courses/storyline-3-player-menu-button-to-trigger-custom-menu-on-the-master-slide#reply-723991
"*Test4Russell.story
<https://articulate-heroes.s3.amazonaws.com/uploads/attachment/attachment
- DanielHollandCommunity Member
When I get to my computer I will look at the exact code I am using and share
- DanielHollandCommunity Member
Okay the following is the exact code I am using. I can only confirm it works in Storyline360 for HTML5 export.
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", "off");
}Again this code goes on every slide that has an input field. The Trigger: Execute JavaScript When timeline starts on this slide.
- DanielHollandCommunity Member
One thing you may have to do is clear your cache. I typically have to hit SHIFT + F5 multiple times to make sure everything is refreshed when testing.
- MarkAnthonyChesCommunity Member
Thanks again!
Ok, it's clearing the chrome autofill from previous input, but the Google
Autofill still works...I really need to find away to get around the input
boxes showing across layers....Help....????