Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.33f1
2022.3.14f1
2023.2.2f1
2023.3.0a16
Issue ID
UUM-57544
Regression
No
Input.GetKey() does not register key release when a specific key is pressed, and then released after opening a context menu
How to reproduce:
1. Open the attached “contextmenu_issue” Project
3. Open the “context-menu-key-held-bug” Scene (Assets/context-menu-key-held-bug) and enter Play Mode
4. Press and hold the ‘W' key
5. Right-click the window header bar
6. Release the 'W’ key
7. Click somewhere in the Game window and observe how the key release has not been registered
Expected result: Releasing the ‘W’ key was registered by the Input system
Actual result: Releasing the 'W’ key was not registered by the Input system
Reproducible on: 2021.3.33f1, 2022.3.14f1, 2023.2.2f1, 2023.3.0a16
Reproducible on: Windows 10, Windows 11
Not reproducible on: No other environments tested
Notes:
* Also reproducible in Player when in windowed mode
* Not reproducible in the new Input system
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
- [UI Builder] Viewport's gizmos for Margin and Padding disappear when dragging to modify the value and the cursor leaves the Spacing section
- "Multiplayer Center" window does not reflect changes made in "Other Packages" section
- Crash on D3DKMTOpenResource when capturing with RenderDoc while GPU Skinning is set to GPU(Batched)
- Editing and saving Curve changes in UI Builder window throws multiple errors in the Console
- [UI Builder] Value is not selected when left clicking on Spacing/Border Widget values
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.