Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2020.3.X
Votes
0
Found in
2020.2.0a12
2020.3
2020.3.1f1
2021.1
Issue ID
1325742
Regression
Yes
Both KeyDown and KeyUp events get invoked upon first mouse click in Game view when it's maximized by context menu setting
Reproduction steps:
1. Open attached project "1325742.zip"
2. Open "SampleScene" Scene
3. Right-click on the Game view Tab to open the context menu
4. Click on "Maximize"
5. Enter Play Mode and click anywhere in the Game view without releasing the mouse button
6. Notice Console messages in the bottom left corner
Expected result: Only the Input.GetKeyDown event is invoked upon the first click and the "KeyDown" message gets printed out
Actual result: Both Input.GetKeyDown and Input.GetKeyUp events are invoked upon the first click and both "KeyDown" and "KeyUp" messages get printed out
Reproducible with: 2020.2.0a12, 2020.3.4f1, 2021.1.0a5
Not reproducible with: 2018.4.33f1, 2019.4.24f1, 2020.2.0a11, 2021.1.0a6, 2021.1.2f1, 2021.2.0a12
Notes:
- Only the first click is causing both events to be invoked, all other clicks after that work fine.
- Maximizing with the "Maximize on Play" button in the Game view doesn't cause this behavior
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 2021.1):
Fixed in 2021.1.0a6
Resolution Note (fix version 2020.3):
Fixed in 2020.3.10f1