Search Issue Tracker
Fixed
Fixed in 2021.3.36f1, 2022.3.20f1, 2023.2.11f1, 2023.3.0b8
Votes
0
Found in
2021.3.34f1
2022.3.17f1
2023.2.7f1
2023.3.0b4
Issue ID
UUM-60384
Regression
No
PointerMoveEvent is not called when dragging the cursor over a UI Document
Reproduction steps:
1. Open the attached "UITKTest" project
2. Open the "Assets/Scenes/BootstrapScene" scene
3. Enter the Play Mode
4. Click and hold on the gray rectangle and drag the cursor around the gray/red area
5. Observe the Console logs
Expected results: Console logs with "OnPointerMoveEvent" continue to appear when dragging the cursor
Actual results: Only 0-1 "OnPointerMoveEvent" Console logs appear and then stops
Reproducible with: 2021.3.34f1, 2022.3.17f1, 2023.2.0a5
Not reproducible with: 2023.2.4f1, 2023.3.0a22
Fixed in: 2023.2.0a6
Reproducible on: Windows 11 Pro
Not reproducible on: No other environments tested
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
- Search field in UI Builder's Library has no character limit
- Changing the value in UI Builder by dragging increases it by a few thousand points when reaching the borders of the screen
- ARM64 architecture DLL incorrectly copied instead of x64 when building for Windows x64
- Crash on TypeTreeIterator::GetNode when opening a specific folder
- Crash on WriteSerializedAssetsV2 when (re)entering the Play Mode in a specific project when IEnumerator Start() is used
Resolution Note (fix version 2022.3.20f1):
By design, during pointer capture as is the case with Button elements, neither Pointer events or Mouse events should be propagated to targets other than the capturing element. We fixed the behavior of mouse events to match that of pointer events, which is not what the bug description suggests but is what should really be happening (according to the design).
Resolution Note (fix version 2021.3.36f1):
By design, during pointer capture as is the case with Button elements, neither Pointer events or Mouse events should be propagated to targets other than the capturing element. We fixed the behavior of mouse events to match that of pointer events, which is not what the bug description suggests but is what should really be happening (according to the design).