Search Issue Tracker
Won't Fix
Votes
5
Found in
2017.4.1f1
2018.3.0a1
2018.3.1f1
2019.1.0a1
Issue ID
1117264
Regression
No
EventSystem/Physics2DRaycaster do not take SortingGroup components into account which causes incorrect event propagation
How to reproduce:
1. Open attached project
2. Observe that the white toggle is visually layered behind the red toggle due to the SortingGroup components
3. Enter the Play Mode
4. Try to click on the red toggle
5. Observe that it is impossible because, if SortingGroups are ignored, the red toggle would layer behind the white toggle (since it has a lower Sorting Order on its SpriteRenderer component)
Reproducible with: 2017.4.18f1, 2018.3.3f1, 2019.1.0a14,
Expected results: Both white and red toggles should be clickable
Actual results: red toggle layers behind and isn't clickable
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (2019.2.X):
Low priority defect for the moment. This bug is unlikely to be fixed in the near future.