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.
Will anyone be looking into this?
Hi Astutis,
I'm happy to help troubleshoot this issue and would like to start with clarifying questions to understand your experience better.
- 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.
- If you see a different behavior, could you send a screen recording so we can understand what's happening?
- 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.
- 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!
Hi Eric.
I raised a ticket with one of your support engineers and they have confirmed it is a bug. Hopefully it get resolved soon :(
Hi Tom,
Thanks for letting me know! I see you've connected with my teammate Cleo who was able to work with you in recreating the issue. I'm sorry that it was a confirmed bug. Our product team will be investigating this, and in the meantime, I'd like to share our process below:
I appreciate your patience!
