Search Issue Tracker
Fixed in 2017.1.X
Votes
1
Found in
5.6.0f3
Issue ID
898158
Regression
Yes
Enabling disabled Prefab instance of nested Canvases results in child UI elements being rendered in wrong position
How to reproduce:
1. Open the attached project "CanvasBug2" and open "CanvasBug2" scene
2. Expand "Main Canvas" GameObject in the Hierarchy and enable SubCanvas prefab instance
Expected result: "SubCanvas3" with Image component is positioned correctly
Actual result: Image component is rendered in wrong position, it seems as it inherits "SubCanvas" position
Notes:
1. Disabling and re-enabling "SubCanvas" prefab instance again, fixes the issue, but only in 5.6 version of Unity
Reproducible with - 5.6.0f3, 5.5.3f1, 5.4.5f1
Not reproducible with - 5.3.8f1
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