Answered

BUG: A Text Input control set to TextMode.Password ignores VirtualKeyboardMode.Numeric

(0) Share

Report

Posted on by JLincoln

Hello,

Regarding the VirtualKeyboardMode implimented from this PowerUsers Idea thread, a text input control where Mode = TextMode.Password overrides the VirtualKeyboardMode = VirtualKeyboardMode.Numeric, even when Format = TextFormat.Number.

I have a use case (and @chchrlam does as well, as they brought it up in the thread that I linked on page 5) where employees log in using their employee ID, and password is set just to help a tad if someone's looking over their shoulder, plus it makes the app look much more professional.

The devices that I'm using are able to use the numeric keyboard in any context other than passwords and VirtualKeyboardMode.Auto usually picks up the number format and handles it nicely. These devices are on Android 10, which is above the settings that @tahoon noted in the thread

Minimum iOS version: 12.2

Recommended Android version: 9.0

Not supported on Windows.

This issue is persistent among a wide variety of devices, and I've tested with phones and tablets; Apple and Android. This issue is clearly not one with my device and is one with the behavior of the Password mode overriding the virtual keyboard mode.

Could this please be fixed, so my users can log in with a ID / PIN number with a cleaner interface rather than the entire keyboard and tiny number values by default? I have a workaround consisting of stacked controls and full transparency but it's slower, much messier, and kind of sad to use.

Thanks,

J

Categories:

Building Power Apps

All responses (2)

Answers (1)

Sort by

Verified answer

tahoon Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hello @JLincoln ,

Power Apps is based on web technologies and depends on devices to implement those standards. In this case, Apple and Android devices use a different keyboard for some reason. You can observe this on any webpage with this HTML.

<input type='password' inputmode='decimal' />

The behavior of Android Chrome and iOS Safari will be the same as with Power Apps. As you point out, this is different from the behavior of a non-password field.

<input inputmode='decimal' />

It will be up to Google and Apple to review this issue.
JLincoln 69 on at

Like
a
(0)

Report
Copy link

Link copied!

Hmm, okay so that implies that in order to fix the problem you'd have to recode the way that passwords get handled to be natively handled within PowerApps rather than the OS level; that's likely too much work for this use-case, which is unfortunate but it's okay.

This isn't a dealbreaker, but it does require the following work around: Have a password control on the bottom and a text (number) control on top. Set the top control to be transparent but don't turn it invisible because you still want to interact with it. Have the user enter their password into it and set the bottom control to be equal to top.Text. This does have the unfortunate side-effect of the user being able to highlight their text and see the actual password, but for my use-case that's fine.

I appreciate your research and solution, @tahoon!