Search Issue Tracker
Won't Fix
Won't Fix in 2021.3.X
Votes
0
Found in
2021.3.30f1
Issue ID
UUM-52667
Regression
No
[AppleTV][UIToolkit] UI navigation gets stuck when selecting a Text Field
How to reproduce:
1. Open the attached Project "textFieldTest"
2. Build and Run the Scene "New Scene" on an Apple TV device
3. In the Player, use the Apple TV Remote to navigate to the Text Field
4. Attempt to navigate to the Button
Expected result: The Text Field loses focus and the Button becomes focused
Actual result: The Text Field remains focused
Reproducible with: 2021.3.30f1, 2022.2.0b15
Fixed in: 2022.2.0b16
Reproduced on:
- Apple TV 4K 1st Generation (tvOS 14.3)
Notes:
- Does not reproduce with TMP Input Fields
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
- UI Toolkit throws warning and fails to clear references when fields are not typed as UnityEngine.Object
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
Resolution Note:
Thank you for bringing this issue to our attention. After careful consideration, we have determined that other higher-priority issues should take precedence, and we have decided not to address your issue at this time. The priority level is determined by factors such as the severity and frequency of an issue and the number of users affected by it.
In this specific case, the work done to support touch screen keyboard should have addressed this. Unfortunately, due to the nature of the work (which includes a refactor on the TextField in addition to other miscellaneous adjustments done to the focus), it is considered too complex and risky to backport to 21.3. We appreciate your input and understanding, and please let us know if you have any other concerns or issues you would like to report in the future.
Resolution Note (2021.3.X):
Thank you for bringing this issue to our attention. After careful consideration, we have determined that other higher-priority issues should take precedence, and we have decided not to address your issue at this time. The priority level is determined by factors such as the severity and frequency of an issue and the number of users affected by it.
In this specific case, the work done to support touch screen keyboard should have addressed this. Unfortunately, due to the nature of the work (which includes a refactor on the TextField in addition to other miscellaneous adjustments done to the focus), it is considered too complex and risky to backport to 21.3. We appreciate your input and understanding, and please let us know if you have any other concerns or issues you would like to report in the future.