Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
0
Found in
2021.3.19f1
2022.2.7f1
2023.1.0b4
2023.2.0a2
Issue ID
UUM-29084
Regression
No
UI element being controlled through Prefab with arrow keys in Play Mode when the Scene view and the Game view are open
How to reproduce:
1. Open the project “IN_29697”
2. Enter the Play Mode
3. Open “PlayerMenu” Prefab in “Assets/Prefabs/UI/Menus”
4. Click on the Game view
5. Press the “Tab” button on the keyboard
6. Press the arrow keys to navigate the menu to the sides
Expected result: navigating with arrow keys through the menu in the Game view
Actual result: navigating with arrow keys through the menu in the Scene view
Reproducible with: 2021.3.19f1, 2022.2.7f1, 2023.1.0b4, 2023.2.0a2
Couldn't test with: 2020.3.44f1 (due to compiler errors)
Reproducible on: Windows 10 Pro
Note: make sure you have Scene view and Game view side by side for easier visibility
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
- Component Glyphs value is truncated and Ligature Table glyph fields become inaccessible when increasing the Component Glyphs count
- There is no “Overwrite Preset?” popup when saving a Customizable Toolbar preset with a name that already exists
- Customizable Toolbar preset does not switch to the Unity Default Preset when Reverting All Saved Presets or deleting the active Preset
- [Usability] Selected node gets unselected when undoing changes in the Graph Inspector Node Settings tab
- Search Default option for Column Format does not reset the column's format
Resolution Note:
After investigation, we have deemed this a low priority issue that won't be fixed in the near future either because it is too costly to implement or because there are risks of introducing other problems doing so.
If you feel this is a wrong assessment, please reach out again, providing more details about the impact of that issue.
Resolution Note (2023.2.X):
After investigation, we have deemed this a low priority issue that won't be fixed in the near future either because it is too costly to implement or because there are risks of introducing other problems doing so.
If you feel this is a wrong assessment, please reach out again, providing more details about the impact of that issue.