Search Issue Tracker
Won't Fix
Votes
0
Found in
2023.3.0b4
Issue ID
UUM-60899
Regression
No
[MacOS] Navigating Create Node menu in VFX Graph with keyboard does not work
How to reproduce:
1. Create a new 3D (HDRP) Project
2. Create a new VFX Graph (Right-click in the Project Window -> Create -> Visual Effects -> Visual Effect Graph)
3. Choose any template
4. Open the newly created VFX Graph
5. Right-click to open the context menu
6. Click the Create Node button
7. Select any parent node in tree view, press enter
8. Observe tree item is still highlighted
Expected result: Navigating the menu with the keyboard works as expected
Actual result: Navigating the menu with the keyboard sometimes does not work when pressing Enter on any tree element makes it so that you cannot open it with the arrow keys.
It is a confusing design to keep the tree item selected as user might expect that usual keymap would still work.
Reproducible with: 17.0.2 (2023.3.0b4)
Reproducible on: macOS Sonoma 14.2.1 (M1)
Bonus issue:
# Press toggle subvariants button
# Press up and down keys
# Observe focus doesn't jump back to a tree view
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
- Artifact ID value changes when reimporting an asset when a mobile platform is selected and Unity Accelerator is enabled
- "Component (...) had become dangling during an undo operation." warning undoing creating a light
- Ghost collisions occur in a Physics mesh when entering the Play mode
- TMP text with Auto Size overflows when using the WD% property
- Light Explorer does not update Isolated Selection when new Light selected in Scene
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.