- From: Emilio Cobos Álvarez via GitHub <sysbot+gh@w3.org>
- Date: Wed, 26 Jul 2023 22:55:54 +0000
- To: public-css-archive@w3.org
The algorithm in Firefox is [here](https://searchfox.org/mozilla-central/rev/bf272a7be6fef0e91bde01dfe1f68403d8fbc237/layout/generic/nsBlockFrame.cpp#939), and in particular `ForceBreak` is what seems to be dealing with floats [here](https://searchfox.org/mozilla-central/rev/bf272a7be6fef0e91bde01dfe1f68403d8fbc237/layout/generic/nsIFrame.cpp#5957). We seem to be preserving more float information than just left / right (we keep actually an array of pointers to all floats). But that might be something that we can just simplify, I haven't looked closely enough to see when it differs from your algorithm. It seems blame for most of that code points to @upsuper (in https://bugzilla.mozilla.org/show_bug.cgi?id=1260031 and https://bugzilla.mozilla.org/show_bug.cgi?id=1322843) and @dbaron (reviewer, and in the original reflow branch), so they may have opinions. Per the comments in the first link above we were mostly trying to match Chromium and EdgeHTML which at the time agreed. -- GitHub Notification of comment by emilio Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9120#issuecomment-1652650644 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 26 July 2023 22:55:56 UTC