I've an issue I can't seem to solve, so I hope you guys can help me.
I've developed an mobile simulation in storyline. When I test this on a mobile device (android and iOS) the data-entry is doing strange things. When I click on it, to fill it in. The screen resizes and you can barely read the text in the field. This happens in the published version in Review and in the web.
I noticed it's because the keyboard appears, the screen resizes. Is there a way to make the screen fixed and the keyboard just overlaps the screen without zooming it out?
Thanks for reaching out and sharing your links. I tested them on a mobile phone and came across the same issue in landscape mode.
I'm sorry that you ran into a bug we have where the keyboard shrinks the text entry box in a mobile device! We have reported it to our team, and continue to keep an eye on it to evaluate how many customers are impacted.
I'm sorry that I can't say when this issue will be fixed, but you're in the right place to stay updated on this bug's progress.
No, you are not. I´m having the same problem and also seen other posts reporting the same issue. This is really bad as it makes impossible for the user to input any text because he or she cannot see it. In other words, makes input text in android mobile phones not viable. Any ideias of when this bug will be fixed?
I'm sorry you're running into this bug as well! Our team is currently prioritizing other bug fixes for upcoming releases. I'll update you in this discussion when our team has prioritized this bug for a future release. I appreciate you taking the time to follow up!
Hello, we're getting a similar issue to which is causing challenges with a few modules that we're hosting. Any idea when it'll be added to the roadmap? It'd be good to not have the zoom element for a mobile when you click into the entry box and the keyboard pops up.
Thanks for checking in, and I'm sorry this bug is impacting your work.
Right now, this one is in the early stages of our How We Tackle Bugs process. To help you plan, it's unlikely to be fixed in the next few updates. We'll let you know if that changes, though!
Let me know if there's anything else I can do. I'm happy to help!
Yeah as i do want to develop Mobile First courses too, i am gonna dive deeper into this issue to figure out what's causing it exactly. Its a year old issue... and apparently not high on Articulate's bugs-to-fix list. What ain't good in my opinion.
Only workaround i found is using a virtual keyboard. Either make one directly in Storyline or use HTML5 and WebObjects to embed one.
https://virtual-keyboard.js.org/ This is a simple and good one. Only extra thing needed in Storyline would be some option to block normal keyboard use.
Hi Math, thanks for your reply! Can you please show me the storyline example for this? My end users keeps reporting us about this issue, there are 5000++ users are using android. I'm stuck. It's working fine couple months ago..
16 Replies
Hi Media,
Thanks for reaching out and sharing your links. I tested them on a mobile phone and came across the same issue in landscape mode.
I'm sorry that you ran into a bug we have where the keyboard shrinks the text entry box in a mobile device! We have reported it to our team, and continue to keep an eye on it to evaluate how many customers are impacted.
I'm sorry that I can't say when this issue will be fixed, but you're in the right place to stay updated on this bug's progress.
Hi Ren,
Thank you for your reply. Too bad there's no work around for it. Hopefully I am not the only one who has troubles with this..
No, you are not. I´m having the same problem and also seen other posts reporting the same issue. This is really bad as it makes impossible for the user to input any text because he or she cannot see it. In other words, makes input text in android mobile phones not viable. Any ideias of when this bug will be fixed?
Hi Will!
I'm sorry you're running into this bug as well! Our team is currently prioritizing other bug fixes for upcoming releases. I'll update you in this discussion when our team has prioritized this bug for a future release. I appreciate you taking the time to follow up!
Hello, we're getting a similar issue to which is causing challenges with a few modules that we're hosting. Any idea when it'll be added to the roadmap? It'd be good to not have the zoom element for a mobile when you click into the entry box and the keyboard pops up.
Thanks, Paul
Hi there, Paul!
Thanks for checking in, and I'm sorry this bug is impacting your work.
Right now, this one is in the early stages of our How We Tackle Bugs process. To help you plan, it's unlikely to be fixed in the next few updates. We'll let you know if that changes, though!
Let me know if there's anything else I can do. I'm happy to help!
Hi Katie, thanks for the update, that's really useful.
We've removed the text edit interactions and replaced them with alternatives as they were too unpredictable for a mass roll out.
Looking forward to hearing which update it'll land in.
Thanks, Paul
Unlikely to be fixed in the next few updates? So Storyline isnot compatible with mobiles and nothing being done about that ?
Its a Android only issue Matthew...
Yeah as i do want to develop Mobile First courses too, i am gonna dive deeper into this issue to figure out what's causing it exactly. Its a year old issue... and apparently not high on Articulate's bugs-to-fix list. What ain't good in my opinion.
It seems so. :(
Anyone here who is able to figure a way out?
Hi Articulate team, it's been 2 years and no update for this issue?
Only workaround i found is using a virtual keyboard. Either make one directly in Storyline or use HTML5 and WebObjects to embed one.
https://virtual-keyboard.js.org/
This is a simple and good one. Only extra thing needed in Storyline would be some option to block normal keyboard use.
Hi Math, thanks for your reply! Can you please show me the storyline example for this? My end users keeps reporting us about this issue, there are 5000++ users are using android. I'm stuck. It's working fine couple months ago..
When i got some spare time i make a working sample.