Search Issue Tracker
Won't Fix
Won't Fix in 2023.1.X
Votes
0
Found in
2023.1.0b12
Issue ID
UUM-33197
Regression
No
[macOS] Mouse.current.leftButton.wasReleasedThisFrame does not get triggered when the button press focuses the Player
How to reproduce:
1. Open the attached Project "input-bug"
2. Build and Run the Scene "SampleScene"
3. Click the left mouse button outside the Build Window to unfocus it (e.g. click on the desktop)
4. Click the left mouse button inside the Build Window
Expected result: "Left pressed" and "Left released" can be seen logged in the Build
Actual result: Only "Left pressed" shows up
Reproducible with: 1.1.1 (2020.3.47f1), 1.5.1 (2020.3.47f1, 2021.3.22f1, 2022.2.14f1, 2023.1.0b11, 2023.2.0a10)
Reproduced on:
- MacOS 12.3 (Intel) Player
Did not reproduce on:
- Windows 10 Player
Notes:
- Clicking inside the Build Window again after reproducing only shows the "Left released" message
- Using Cmd+tab or clicking on the Dock icon of the Build to focus the Player makes the issue not reproducible
- Unable to test other Inputs, as only the left mouse button focuses the Player
- Does not reproduce in Editor
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
- MissingReferenceException errors are thrown after entering Play mode when multiple Inspector windows are displaying different objects with Grid Layout Group component
- "Can't change name, category with the same name already exists" Error is logged when renaming a Category to a name with a trailing space in the VFX Graph Blackboard
- Delete does nothing on an in-use Custom Attribute when re-triggered after cancelling the deletion confirmation prompt in the VFX Graph Blackboard
- No Ellipses are used for the Visual Effect Graph Create Context Menu Option
- Crash on LaunchBugReporter when opening a specific project using DirectX 12
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 (2023.1.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.