Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
1
Found in
2020.3.30f1
2021.2.15f1
2022.1.0b11
2022.2.0a7
2023.1.0a3
2023.2.0a1
Issue ID
UUM-3531
Regression
No
Incorrect child clipping after destroying parent Canvas that has Override Sorting enabled and is a child of Rect Mask 2D
Reproduction steps:
1. Open the user's attached project "bugreport.zip"
2. Enter Play mode
3. Click the "Destroy Child Canvas" button in the Game view
Expected result: The "Image" GameObject is clipped by the "Container" GameObject
Actual result: The "Image" GameObject is not clipped by the "Container" GameObject
Reproducible with: 2019.4.36f1, 2020.3.30f1, 2021.2.15f1, 2022.1.0b11, 2022.2.0a7
Note: Disabling and reenabling "Image" in the Inspector window will correct the clipping
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
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
Resolution Note:
After investigation, we have deemed this a low priority issue that won't be fixed in the near future either because it is too costly to implement or because there are risks of introducing other problems doing so. There's also a way to work around the issue (disabling and reenabling).
If you feel this is a wrong assessment, please reach out again, providing more details about the impact of that issue.
Resolution Note (2023.2.X):
After investigation, we have deemed this a low priority issue that won't be fixed in the near future either because it is too costly to implement or because there are risks of introducing other problems doing so. There's also a way to work around the issue (disabling and reenabling).
If you feel this is a wrong assessment, please reach out again, providing more details about the impact of that issue.