Search Issue Tracker
Fixed in 5.2.0
Votes
0
Found in
5.1.0b3
Issue ID
690612
Regression
No
[PointerHandlers] Pointer enter/exit detection order is not working correctly with sorting layers
Steps to reproduce:
1. Open the attached project
2. Open 'EventSystemBug' scene
3. Notice that three sprites are rendered corretcly according to the 'Sorting Layer' properties set
4. Play the scene
5. Hover the mouse on these sprites
Expected behavior: OnPointerEnter and OnPointerExit should be called with the same order the sprites are rendered.
Actual behavior: OnPointerEnter and OnPointerExit functions gets called without taking sorting layer into account.
Workaround: Place all the sprites in the same Sorting Layer and change their 'Order in Layer' values to match the wanted rendering result. Notice that now the mentioned functions get called as expected.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment