Search Issue Tracker
Fixed
Fixed in 6000.4.0b1, 6000.5.0a3
Votes
0
Found in
6000.0.63f1
6000.2.13f1
6000.3.0f1
6000.4.0a5
6000.5.0a2
Issue ID
UUM-128103
Regression
No
Command remains bolded after removing assigned shortcut
Reproduction steps:
1. Create a new project
2. Unity > Shortcuts…
3. Assign a shortcut to command that does not have a shortcut by default
4. Right-click on the command and select “Remove shortcut” option
5. Observe the command
Actual result: Command remains bolded even though it did not have a shortcut by default
Expected result: Command is not bolded
Reproducible with: 6000.0.63f1, 6000.2.13f1, 6000.3.0f1, 6000.4.0a5, 6000.5.0a2
Reproduced on: macOS Tahoe 26.1 (M4)
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
- “Default state” name in Inspector is not truncated when given longer name for “New State” in Animator window
- Upgrading HDRP Project causes the Cloud Layer to warp when using the Global Volume with the Visual Environment enabled
- The Inspector does not shown SkinnedMeshRenderer Bounds when they are overriden by script
- Confusing validation message in Scoped Registries
- Compute shader is dispatched with unsupported workgroup size on multiple browsers when building the project for Web with WebGPU Graphics API
Resolution Note (fix version 6000.5.0a3):
Fixed a bug where removing an empty shortcut would be shown as an override in the Shortcut Manager.
Resolution Note (fix version 6000.4.0b1):
Editor: Fixed a bug where removing an empty shortcut would be shown as an override in the Shortcut Manager.