Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.1.0b9
2017.3.0b9
Issue ID
969471
Regression
Yes
Child Controls Size field in Layout Groups behaves the opposite when ticking/unticking
To reproduce:
1. Open attached project
2. In Hierarchy window, select LayoutPanel game object
3. In Inspector window, check Child Controls Size parameter in Layout Group component
4. In Hierarchy window, select LayoutChild
5. In Inspector window, check child's Rect Transform component
Expected: LayoutChild is not allowed to be resized when Child Controlls Size field is unticked (and vice versa)
Actual: LayoutChild can be resized when Child Controlls Size field is unticked (and vice versa)
Reproduced in: 2017.1.2p3, 2017.2.0p2, 2017.3.0b10, 2018.1.0a5
Not reproduced in: 5.5.5p1, 5.6.4p2
Note: field name was changed from "Control Child Size" to "Child Controls Size" and back, inverting it's meaning several times between 5.6 and 2017.1
Note: check .gif attached for issue reproduction
Comments (1)
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
spierce_unity278
Jun 05, 2019 16:51
Is this still true? Everything about this feature is confusing and there is no real documentation for it.