Search Issue Tracker
Won't Fix
Votes
0
Found in
2020.3.36f1
2021.3.5f1
2022.1.8f1
2022.2.0a18
2023.1.0a1
Issue ID
UUM-7745
Regression
No
[Windows] Input.GetKeyUp is true only for the first released mouse button when releasing mouse buttons outside the Game view
Reproduction steps:
1. Open the attached “MouseButtons” project
2. Open the “SampleScene” scene
3. Enter Play Mode
4. Press the left and right mouse buttons
5. Move the cursor outside the Game view
6. Release the right mouse button
7. Release the left mouse button
8. Observe the Console
Expected result: “KeyUp: Mouse0” is logged
Actual result: “KeyUp: Mouse0” is not logged
Reproduced in: 2020.3.36f1, 2021.3.5f1, 2022.1.8f1, 2022.2.0a18, 2023.1.0a2
Reproduced using: Windows 10, Windows 11
Not reproduced using: macOS 13.4 (Intel)
Notes:
1. The reporter also reproduced in WebGL
2. Not reproduced in Windows Player
3. Not reproduced with keyboard keys
4. Also reproduced with the right mouse button
5. KeyDown isn’t called when pressing the left mouse button in Game view for the first time after reproduction (Unity thinks it’s still pressed even though physically it’s not)
6. OnApplicationFocus and OnApplicationPause do not return true during reproduction, indicating that the Game view does not lose focus
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
- 3D Sample Scene (HDRP) template tutorial Welcome Dialog pop-up doesn't appear on project creation
- [Profiler] The Addressable Asset Module module outputs an ArgumentException when asset GUIDs produce a hash collision with Addressables
- Huge amounts of tests have a start delay when pressing "Run All" in the Test Runner
- Blackboard: Double borders around the tooltip
- [WebGL]VideoPlayer Rendering stops when setting FilterMode of a texture downloaded with UnityWebRequestTexture.GetTexture()
Resolution Note:
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix". This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.