Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.2.10f1
Issue ID
1087109
Regression
No
Input.mousePosition doesn't track right mouse click outside of game window when game resolution exceeds monitors resolution
Steps to reproduce:
1. Open attached project "case_1087109-dragtest.zip"
2. Build and Run (on Chrome)
3. Right-click and drag out of the game window
Expected result: Input.mousePosition still tracks mouse position when outside of the game window.
Actual result: Input.mousePosition only returns the last point at which the cursor was before leaving the game window.
Reproduced in: 2017.4.14f1, 2018.1.9f2, 2018.2.14f1, 2018.3.0b8, 2019.1.0a7
Note: Bug reproduces on the newest version of Chrome (69.0.3497.100; 64-bit) and older version of Mozilla Firefox (47.0.2).
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note (2019.1.X):
This is a browser specific issue, and a relatively low impact issue for most developers. Unlikely to be fixed any time soon.