Search Issue Tracker
Fixed in 5.3.5
Votes
0
Found in
5.3.1p1
Issue ID
769666
Regression
No
[Standalone] UI elements on the edge of the screen still get mouse over input when your mouse is outside the window
Steps to reproduce:
1. Open attached project
2. Open scene "Main"
3. Notice that there's a button which isn't fully inside canvas
4. Build and run scene
5. Run in windowed mode
6. Move mouse outside of window and them move towards the button
7. Notice that button is highlighted even though mouse is outside game window
Reproduced with: 5.1.4f1, 5.2.4p1,5.3.2p3, 5.4.0b5
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
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
Dan-MacDonald
Aug 31, 2016 18:27
It seems the EventSystem.RaycastAll() returns hit results for elements that are partially onscreen, even when the raycast hit position is happening outside the window.
Ewanuk
Aug 11, 2016 14:32
Still have this issue in 5.3.5f1
RobertWebb
May 27, 2016 02:17
There are two new problems I see in our app which may be because of this fix:
(1) We navigate our app on Windows desktop by holding down the left mouse button and dragging the mouse. When we drag outside the window, the previous clamping behaviour gave more expected results. Rather than either clamping or locking to the last point in the window, why not do the "usual" thing and capture the mouse position, even outside the window? See Microsoft's SetCapture() and ReleaseCapture() functions. This would give correct behaviour AND fix the original problem.
(2) When running in the Editor, if I drag the mouse past the left side of the window, it suddenly acts as if it's on the far RIGHT of the window! So I'll be panning left and suddenly it will switch to panning fast right. Clearly this is a new bug. Only started doing this in 5.3.5, not in 5.3.4.
Thanks,
Rob.