Help!
One of my guys created a mobile prototype that we thought was going to be tested in a phone frame on desktop. It works fine on desktop, but when we open it on a phone we can’t click into the text boxes to enter data.
Any ideas?
Text boxes not accessible on mobile
mike1366
#2
A standard text field should work fine on mobile. Which mobile OS and browser are you using? Can you share the prototype on Axshare? Are you hiding content on top of the text fields or using complex dynamic panel states that might be causing issues on mobile?
mbc66
#3
It would help others help you a lot quicker if you could post your .rp file here. If that’s it possible then a brief recreation of the problematic part could help. Next best thing is screenshots of the applicable widgets and interaction code, maybe along with prototype shots. If you don’t want to post any of it you can send the .rp file to support@axure.com and they might be able to help.
In general, OnClick events are handled the same in mobile as in desktop. Are you using the Axure Share app for mobile?
Very hard to guess how your prototype might be constructed or what exactly is going on with your events and actions. Are your “text boxes” Text Field or Text Area widgets? Or Rectangle widgets? Are they handled with OnClick, OnMouseDown, OnMouseUp? Are they buried in dynamic panels, etc?
nkrisc
#4
It’s pretty impossible to tell you what might be wrong with more details. Here’s a few shots in the dark:
- Do you use adaptive views? Is an invisible widget accidentally covering the field in the mobile view but not on desktop?
- Are you using any OnFocus or other interactions that maybe, somehow, someway could be causing weird things to happen?
- What phone? All phones and mobile browsers? Could be an OS or browser specific issue?
If you’re reluctant to share your file, can you copy paste only the affected widgets into a blank file and anonymize it (this will also help you troubleshoot by seeing if the issue remains or not)? Or you could also email it to Axure Support privately.
scarpi21
#5
We’re pretty sure the problem is baked in the large amount of dynamic panels we are using. Will post back with findings.
nkrisc
#6
If you have any suspect panels, you can give them solid backgrounds to help make troubleshooting easier. It would help you see if any are covering your field.
