Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
2019.4
2020.3
2020.3.20f1
2021.1
2021.2
2022.1
Issue ID
1374169
Regression
No
Input.GetKey() returns true for Alt key after Alt+Tabbing and reopening Build during Coroutine
Reproduction steps:
1. Open the user attached project
2. Build the project with Autoconnect Profiler enabled
3. Run the Build
4. Click the "Do Big Calculation" button
5. Immediately press left Alt+Tab to switch windows then open the Build again
Expected result: Debug logs left Alt key being down as false
Actual result: Debug logs left Alt key being down as true
Reproducible with: 2019.4.31f1, 2020.3.20f1, 2021.1.26f1, 2021.2.0b16, 2022.1.0a13
Notes:
1. Reproducible in Play Mode
2. Tapping Alt will fix the result
3. Clicking on other windows will fix the result
4. If the Build is not responding during Coroutine, wait for a bit
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note:
Postponing until further notice due to higher priority needs. We hope to revisit this at a later time.