Search Issue Tracker
Fixed in 2022.1.X
Votes
1
Found in
2020.3.19f1
2021.2.0b17
2021.2.2f1
2022.1.0a7
Issue ID
1381688
Regression
Yes
Shortcut Conflict popup window is blank when pressing a hotkey that's assigned to multiple MenuItem attributes
How to reproduce:
1. Open the attached project "Input_Bug_Repro.zip"
2. Press shift + command + G (shift + control + G on Windows)
3. Observe the Shortcut Conflict popup
Expected result: Shortcut Conflict popup is not blank
Actual result: Shortcut Conflict popup is blank
Reproducible with: 2020.3.19f1, 2020.3.20f1, 2021.2.0b14, 2021.2.0b17, 2021.2.4f1, 2022.1.0a7, 2022.1.0a9
Not reproducible with: 2019.4.31f1, 2020.3.18f1, 2021.2.0b15, 2021.2.0b16, 2022.1.0a6, 2022.1.0a10, 2022.1.0a16
Notes:
- Sometimes the Shortcut Conflict popup window will not be blank, repeating the reproduction steps one more time will open a blank Shortcut Conflict popup window
- Pressing inside the Shortcut Conflict popup window makes it come back to normal
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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Resolution Note (fix version 2022.1):
Fixed in: 2022.1.0a10