Why were floats historically cleared and what modern alternatives avoid clearfix hacks?

Why were floats historically cleared and what modern alternatives avoid clearfix hacks?

• A. Floats always contribute to the parent's height.
• B. Floats do not contribute to the parent's height; modern alternatives include overflow: hidden; display: flow-root; or using flex or grid.
• C. Floats clear themselves automatically.
• D. Floats only affect inline content.

Answer: (B)

Floats are taken out of the normal document flow, so a container’s height won’t automatically include them. That’s why, historically, people used clearfix techniques to force the container to wrap around the floated children. Modern CSS gives cleaner ways to achieve the same result without extra markup. Setting overflow to hidden or auto creates a new block formatting context, which makes the container enclose the floats. Using display: flow-root does the same in a more explicit way. Or, switch to a layout model like flexbox or CSS grid, where the container’s height is governed by the layout, not by floated elements. All of these approaches prevent the parent from collapsing and avoid clearfix hacks.

Floats are taken out of the normal document flow, so a container’s height won’t automatically include them. That’s why, historically, people used clearfix techniques to force the container to wrap around the floated children. Modern CSS gives cleaner ways to achieve the same result without extra markup. Setting overflow to hidden or auto creates a new block formatting context, which makes the container enclose the floats. Using display: flow-root does the same in a more explicit way. Or, switch to a layout model like flexbox or CSS grid, where the container’s height is governed by the layout, not by floated elements. All of these approaches prevent the parent from collapsing and avoid clearfix hacks.