Search Issue Tracker
Fixed in 5.6.0
Votes
1
Found in
5.4.3p1
Issue ID
864367
Regression
Yes
[UI]Disabling a nested canvas inside another nested canvas moves the Image components of the child canvas gameobjects
Steps to reproduce:
1. Download and open the attached project
2. Disable the "Nested1" gameobject
3. Enable the "Nested1" gameobject
Expected result: nothing happens
Actual result: image components of UI element get moved up
Reproduced on: 5.4.3p1, 5.4.4f1, 5.5.0p3, 5.6.0b3
Not reproduced on: 5.3.7p2
Bug first appears in 5.4.3p1
Notes:
-this applies to any elements that have an Image component
-this is "fixed" by disabling and enabling the Nested canvas whose elements get moved
-the process can be repeated infinitely by nesting Canvases. The direction (up/down) is alternating with every canvas
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
- [UIBuilder] Changes aren't detected on types implementing IList
- [HDRP] Text is rendered with artefacts when using STP and resolution scale is set a float value
- [Settings Search] Search results not always matching search term correctly
- Crash on memcpy when opening a project that loads TSS files
- Multiple errors appear when compiling a ShaderGraph shader's code in a specific project
n_papkov
Aug 21, 2017 14:57
I reproduced the same bug at 5.6.1f1. I have many nested canvases with different 'Sorting order', but on top displays the last instantiated canvas and when i disabling and enabling canvases they begin take into consideration 'Sorting order'
achrenico
Jan 25, 2017 14:25
This bug was introduced in 5.4.3p1, could it be backported to 5.4 or 5.5? 5.6 is still in beta.