Mobile browser keyboard on select multi line text input
Apr 18, 2019
By
JUSTIN FINN
Hi, I am having some trouble with a multi line textinput field.
This is a SCORM produced by an outside source, using storyline. When attempting to enter text into a multi line textinput field, the mobile device keyboard appears only if we select the top line of the area of the textinput.
I looked in the zip file and found where the field is defined and it does have a height greater than a single line of text - is this something anyone else has seen? I would like to be able to help the producer to fix the problem and republish but I do not have a lot of experience with this format.
thanks in advance!
5 Replies
Another detail - this is an html5 project and I find the same behavior on an iPhone and an android device.
Hi Justin,
Thanks for reaching out and letting us know what you're running into with your published output on mobile devices.
Do you know what version of Storyline you're using? We are currently on Build 3.26.18601.0 for Storyline 360. You can read all of the details here.
You can check by going to:
Help > About Articulate Storyline
I see where we had a previous issue reported, but it is marked as fixed in Update 22.
Hi, sorry about this, the user that made this was actually using presenter.
I looks like if I import to storyline and use the modern browser everything works - the only issue is that the project does not completely import correctly - some syncing issues with his animation.
So, it looks like when I load the quiz section in quezmaker we can see that the multiline text area is not selectable on a mobile device - one must click only the top line to focus on the text area.
Is there any way around this?
Hello Justin,
Thanks for letting me know that you are experiencing an issue with selecting the text area in Quizmaker as well.
I've not seen reported for Quizmaker, but I was able to replicate so I'm reporting the issue for you. I'll attach this conversation so that we can share any updates as well.
I wanted to share some information about how we manage these feature requests as that may be helpful.
No workarounds listed other than using the first line to select.
This discussion is closed. You can start a new discussion or contact Articulate Support.