Nested VerticalLayoutGroup configuration

I have a vertically scrollable UI panel (part of a ScrollView) that contains entries that have different heights. The entries are data records comprised of X number of fields. I have the panel scrolling properly, but I can’t get the entries to recompute their height and properly render.

I could use advice on how to structure the elements and configure the component settings to get this to work.

Here’s my current element hierarchy. I’ve tried adding a ContentSizeFitter to the Entry elements. The entries do resize, but they don’t stack up in the panel as they should. They’re placed on the top of the panel, out of view. There’s also a warning about being part of parent layout group…

Content Panel - VerticalLayoutGroup (no child force expand), ContentSizeFitter (vertical preferred size)
    Entry 1 - CanvasRenderer, Image, VerticalLayoutGroup (no child force expand), LayoutElement (flex height)
        Header - CanvasRenderer, TextMeshProText
        Field 1 - CanvasRenderer, Image
            Label - CanvasRenderer, TextMeshProText
            Value - CanvasRenderer, TextMeshProText
        ...
        Field n - CanvasRenderer, Image
            Label - CanvasRenderer, TextMeshProText
            Value - CanvasRenderer, TextMeshProText
    ...
    Entry m - CanvasRenderer, Image, VerticalLayoutGroup (no child force expand), LayoutElement (flex height)
        Header - CanvasRenderer, TextMeshProText
        Field 1 - CanvasRenderer, Image
            Label - CanvasRenderer, TextMeshProText
            Value - CanvasRenderer, TextMeshProText
        ...
        Field n - CanvasRenderer, Image
            Label - CanvasRenderer, TextMeshProText
            Value - CanvasRenderer, TextMeshProText

As is often the case, I found the solution minutes after posting the question.

The solution is to set Control Child Size->Height to true in the VerticalLayoutGroup on the Content Panel.

It works, so I’m happy. However, I don’t understand why. It took me a long time to even try this because having the parent container control the size of the children doesn’t make sense, since the children determine their own sizes based on the contents of their own VerticalLayoutGroups. Is “Control Child Size” poorly named? Does it actually mean something like “Defer Size to Child”?