This is intented. When we override the contentContainer property of a control, the contentContainer's physical children become the control's root's logical children. The logical parent of the elements under that contentContainer are now the control's root directly, and the contentContainer element is no longer part of its physical children's logical hierarchy, so its USS classes are not visible when processing the children's style.

This behavior enforces the contentContainer abstraction, where there should be no impact to an element's styling if we insert additional elements between the control's root and its logical children. The ScrollView for example has multiple levels of hierarchy between the ScrollView's root and its logical children, but the exact details of that hierarchy shouldn't be taken into account when interacting with the ScrollView.

In this ticket's reproduction project, the fact that one of the table's column was used as the contentContainer element means that that column's specific USS classes are not visible to the elements inside the table, because their logical parent is not the column anymore, but rather it's the table directly. However, some styles like the `color` style are inherited by nature, and because of that they are applied from the column element directly, which happens outside of the contentContainer abstraction, so in that case the color style seems to be applied to the logical children correctly. However, the color style is not applied to the logical children directly; it's just inherited.