Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.12f1
Issue ID
UUM-54919
Regression
Yes
Input Fields lose keyboard focus when the virtual keyboard is moved on Hololens 2
How to reproduce:
1. Open the attached project "KeyboardMRTKTest.zip"
2. Build the project for UWP
3. Open the built Solution
4. Start Debugging with "Debug, ARM64" settings
5. In HoloLens 2 select one of the Input Fields
6. Type "a" with the virtual keyboard
7. Move the virtual keyboard by pinching and moving the edge of the virtual keyboard
8. Repeat step 6
Expected results: The keyboard still types into the previously selected input field
Actual results: The keyboard does not type into any input field
Reproducible with: 2022.3.12f1
Not reproducible with: 2021.3.32f1
Could not test with: 2023.1.19f1 (compilations errors while deploying to HoloLens 2), 2023.2.0b16, 2023.3.0a12 (compilations errors in the Console window)
Reproducible on: HoloLens 2
Not reproducible on: No other environment tested
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
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
Resolution Note:
The supplied reproduction project is using both the Input Manager and System, but also the older UIInputModule on its EventSystem.
To get the correct behaviour, on the canvas' EventSystem, replace the Standalone Input Module with InputSystemUIInputModule.