Search Issue Tracker
Fixed in 2017.1.X
Votes
0
Found in
5.6.0f3
Issue ID
905518
Regression
Yes
overrideSorting property is not set if an object was parented to a Canvas and a Canvas component was added to it
If the game object was first parented to a Canvas and then the Canvas component was added to it, the overrideSorting property cannot be set. However, if the Canvas component was added to the object before parenting it to another Canvas, overrideSorting property will be set properly.
To reproduce:
1. Open the project, attached by the tester (overrideSortingBug.zip)
2. Open the "scene" scene
3. Enter Play mode
4. Observe the "new Canvas" game object's Canvas component, overrideSorting will be false (should be true)
Expected: overrideSorting property is set properly with any order of operations
Reproduced in 5.6.0f1, 5.6.0f3
Did not reproduce in 5.5.4f1, 5.6.0b11, 5.6.1f1, 5.6.2p2, 2017.1.0f2, 2017.2.0b2
Regression introduced in 5.6.0f1
Fixed in 5.6.1f1
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