- From: davidsgrogan via GitHub <sysbot+gh@w3.org>
- Date: Tue, 19 Nov 2024 22:38:09 +0000
- To: public-css-archive@w3.org
> I don't see the problem with following floats, they can't affect whether margins are adjoining, right? Wouldn't they affect if bottom margins are adjoining? ```html <div style="outline: solid; width: 100px; height: 100px;"> <div style="height: stretch; margin: 10px; display: flow-root;"></div> <div style="float: left; width: 30px; height: 30px;"></div> </div> ``` > Only preceding floats can do it, depending on whether they trigger clearance on our element. And I initially thought this would be easy to handle (Servo doesn't parallelize BFCs with floats), but if the element has an aspect ratio, then a definite block stretch size can affect its inline size, which can affect whether it needs clearance, which can affect the block stretch size. I think `width: max-content` column-wrap flexboxes have the same block-size-affects-inline-size problem. But, yes, this difficulty is why I brought it up to Tab :) > But note that it's not just preceding floating siblings, they could be uncles or such. Oof, good point. This makes Tab's ["other way" proposal](https://github.com/w3c/csswg-drafts/issues/11044#issuecomment-2486584397) look attractive for ease of implementation; we say margin adjoining-ness isn't affected by any preceding floats at all. Which means more overflowing will happen in the wild, compared to if we say any preceding float, no matter where they are in the BFC, will disable adjoining-ness. -- GitHub Notification of comment by davidsgrogan Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11044#issuecomment-2486894291 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 19 November 2024 22:38:10 UTC