Search Issue Tracker
Fixed in 14.0.2
Fixed in 13.1.7
Votes
1
Found in [Package]
8.1.0
Issue ID
1396759
Regression
Yes
[ShaderGraph] Can't navigate the node creation menu with keyboard while search is focused
Steps to reproduce:
1. Create a new project
2. Install ShaderGraph through the Package Manager
3. Create a new ShaderGraph and open it
4. Once the graph is open, press "Space" on the keyboard to open the node creation menu
5. Start typing in "Gradient"
5. Press "Enter" key on the keyboard to select the highlighted node
Expected result: The node that was highlighted is created
Actual result: Nothing happens, key inputs are going to the search text field
Reproducible with: ShaderGraph 8.1.0 (2020.2.0a17), 10.8.1 (2020.3.27f1), 13.1.4 (2022.1.0b4), 14.0.0 (2022.2.0a3)
Not reproducible with: ShaderGraph 7.7.1 (2019.4.34f1), 8.0.1 (2020.1.0b1) (Different selection menu, but all keyboard inputs are intuitive and go to the selection menu), 12.1.4 (2021.2.10f1)
Notes:
- Tested with macOS
- This affects not only enter, but the whole navigation, like going through the list with up/down arrow keys
- Keyboard navigation works if the list is focused by selecting any element in it with a mouse click
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
- Build fails when building with ILCPP Scripting Backend and ARMv7 as the Target Architecture
- Textures turn black in Player when they are referenced by a script instance
- [Android] Virtual device crashes with "Scudo ERROR: invalid chunk state when deallocating address" error in Firebase Test Lab when Optimized Frame Pacing is enabled
- Particle System does not resume when its Culling Mode is set to "Pause" or "Pause and Catch-up," and particle position simulate in world space
- "Custom Render Queue" field cannot be set above "2000" when changing it in the Inspector window using Debug mode
Resolution Note (fix version 14.0.2):
ShaderGraph 14.0.2 is available from 2022.2.0a10 onwards
Resolution Note (fix version 13.1.7):
Fix is available on 2022.1.0b16 and onwards