> My point is really that I am not even sure what I would > expect to happen in such cases. The same thing as happens if you just delete the parent element fro

> My point is really that I am not even sure what I would > expect to happen in such cases. The same thing as happens if you just delete the parent element from the source (if we ignore for the moment selector matching and inheritance). > with what seems to be nominal, if not decreasing, gains. display:contents was pretty commonly requested by component authors who want their component to fit into a larger layout framework (flex, grid, table) as more than one layout unit. I agree that if you're not trying to author components it's of pretty limited utility.