Millisecond Forums

nextbuttonposition not working on Android

https://forums.millisecond.com/Topic36842.aspx

By AKrishna - 1/28/2025

Hi all,

a colleague is running data collection on Android Huawei tablets and has noticed that often, the "next" button on a surveypage can be activated even when the on-screen keyboard is covering it. This means participants will often jump forward when they are actually trying to hit the space key as they enter a text response. We're not sure what's causing this issue, but we wanted to work around it for the current round of data collection by moving the nextbutton to the top right of the screen with the /nextbuttonposition attribute.

When we do this (/nextbuttonposition = (85%, 5%)), it works on a PC test run, but the button does not change position on the tablets. Is there anything we can do about this?

Thanks for any assistance!
By Dave - 1/28/2025

 
AKrishna - 1/28/2025
Hi all,

a colleague is running data collection on Android Huawei tablets and has noticed that often, the "next" button on a surveypage can be activated even when the on-screen keyboard is covering it. This means participants will often jump forward when they are actually trying to hit the space key as they enter a text response. We're not sure what's causing this issue, but we wanted to work around it for the current round of data collection by moving the nextbutton to the top right of the screen with the /nextbuttonposition attribute.

When we do this (/nextbuttonposition = (85%, 5%)), it works on a PC test run, but the button does not change position on the tablets. Is there anything we can do about this?

Thanks for any assistance!

On touch-screen devices, the location of the navigation button cannot be changed. It will always be located at the bottom of the screen. I seem to be unable to reproduce the issue you describe (hitting the space key on on-screen keyboard results in tap on navigation button instead), but perhaps there is something peculiar about the default on-screen keyboard shipped by Huawei. Perhaps installing a different keyboard and setting that as the default on those devices might help.