Search Issue Tracker
Won't Fix
Won't Fix in 1.4.X
Votes
0
Found in [Package]
1.4.4
Issue ID
ISXB-341
Regression
No
InputAction.IsPressed is behaving incorrectly when the Game view window is undocked
How to reproduce:
1. Open the attached project "GameViewInputTest.zip"
2. Enter Play Mode
3. Undock the Game view window
4. Press and release the left mouse button on the Game view window header
Expected results: "Action Is Pressed:" returns false
Actual results: "Action Is Pressed:" returns true
Looking at the Input Debugger we the leftMouseButton value stays at '1' even after releasing the mouse button during step 4.
Reproducible with: 1.3.0 (2020.3.37f1), 1.4.1 (2020.3.37f1, 2021.3.8f1, 2022.1.13f1, 2022.2.0b4, 2023.1.0a5)
Reproducible on: Windows 10 & 11
Not reproducible on: MacOS 12.6
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
- Animator state transition preview clips are flickering when zooming in
- [Tile Palette] Sprites not rendering when brush tool "Paint a filled box with active brush" is used for the first time
- Adding available Nodes with longer names in Fragment Context window overflow Fragment Context window in Shader Graph
- "Layer Palette Profile" Asset is automatically applied to the second Terrain but doesn't load any layers
- "Terrain Tools" shortcut conflicts with the Overlays shortcut by default
Resolution Note:
Thank you for your bug report.
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.
Resolution Note (1.4.X):
Thank you for your bug report.
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.