Search Issue Tracker
Fixed in 2021.2.X
Fixed in 2019.4.X, 2020.3.X, 2021.1.X
Votes
4
Found in
Issue ID
1320676
Regression
No
[UWP] TouchScreenKeyboard shows word suggestions for Password and other 'secure' input fields
The Windows OnScreenKeyboard typically shows word suggestions as you enter in characters along the top bar of Keyboard UI. However, for "Password" or other input fields that hold sensitive information, it shouldn't show these suggestions. Currently though, when entering text into a Unity InputField or TextMeshPro with a Password context, word suggestions will still appear and can even display the password string itself.
Steps:
1. Open the attached Unity project
2. Build for UWP and run the app
3. Click on the top InputField, which has a "general" context
4. *Open the Windows Soft Keyboard and start entering in characters/words
5. Notice word suggestions will appear in the top bar as you type
6. Click on the bottom InputField, which has a "password" context
7. *Again open the Windows Soft Keyboard and enter in characters
Expected: The word suggestion will NOT appear when entering text into the bottom InputField
Actual: Word suggestion do appear, which might include the Password string itself
*Enable the Keyboard icon by right-clicking the Taskbar and enable "Show touch keyboard button" option. Simply click this icon (after focusing a given InputField) to display the Soft Keyboard and enter text.
NOTE: Due to some other issues with Windows Soft keyboard currently being fixed, word suggestions may not appear or briefly flicker on before disappearing. If this happens, enter some characters and then backspace over them; word suggestions will appear once the InputField is empty again.
This issue was first raised as a MRTK Issue: https://github.com/microsoft/MixedRealityToolkit-Unity/issues/8723, but it applies to all UWP apps and not just HoloLens.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
vlad_librestream
Mar 29, 2021 15:36
We need to fix it asap since it's a serious privacy breach in the MRTK keyboard.