Search Issue Tracker
Fixed in 2018.2.X
Fixed in 2017.3.X, 2017.4.X, 2018.1.X
Votes
21
Found in
2017.3.0b5
2017.3.0f2
Issue ID
977959
Regression
Yes
Turning off a child object in Canvas, applying changes to prefab, then turning on again breaks it's layout
This is happening only when an object with TextMeshPro components are used in the Canvas.
Steps to reproduce:
1. Open QA's attached project
2. Open scene "Main"
3. Select "Background" under Canvas\ComplexPrefab in the Hierarchy
4. Disable it and apply changes to prefab
5. Enable "Background"
Expected result: Layout stays unchanged
Actual result: Layout completely messes up
Reproduced with: 2017.3.0b5, 2017.3.0f3, 2018.0a7
Not reproduced with: 5.6.4p4, 2017.1.2p4, 2017.2.1f1, 2017.3.0b4
Regression introduced in 2017.3.0b5
Comments (19)
-
toshbaird
Jan 25, 2018 22:37
Is there an ETA for when a patch will be available with this fix in it? This is pretty urgent and is affecting a lot of people by the looks.
-
rankornfeld
Jan 16, 2018 07:06
So is there any latest stable version we can use where this issue is fix??
-
DeadReckoned
Dec 29, 2017 08:44
Encountering this issue even when *not* using TextMeshPro components - Layout for deactivated objects are broken when prefabs are applied.
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
- Uninitialized variable warning appears in the Inspector of a custom shader when the variable is initialized
- "Failed creating toolbar element from ID..." error is thrown when resetting the Scene view Overlay layout while an Asset Transformer Toolbox overlay is active
- Entity ID for Font Assets is serialized twice which throws an error when using Debug Inspector
- Play Mode can be entered when disabling Adaptive Performance and pressing either the Play Mode button or the keyboard shortcut to enter Play Mode before recompilation leading to errors and warnings thrown
- Parent ListView element also becomes selected when inner ListView element is selected
karl_jones
Jan 29, 2018
The fix for this will be available in 2017.3.1p1