W3C home > Mailing lists > Public > public-css-archive@w3.org > October 2019

Re: [csswg-drafts] Do fragments float independently? (#4434)

From: L. David Baron via GitHub <sysbot+gh@w3.org>
Date: Tue, 22 Oct 2019 23:06:50 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-545192895-1571785609-sysbot+gh@w3.org>
So I remembered Gecko code that I thought tried to position later fragments of floats based on where (in the inline-axis) they were in earlier fragments.  But maybe I'm misremembering.

I'd also note that the spec should probably go into more detail on what the rules for positioning of floats mean in the presence of fragmentation.  The Gecko implementation tries to interpret them, but it should probably be clearer.  For example:
* The [rules](https://www.w3.org/TR/CSS21/visuren.html#float-rules) constraining the "outer top" of a float mean that if one of the things that the "outer top" can't be higher than is pushed to the next fragment, then the float must do so as well, as a matter of logically extending the rules for float positioning to a fragmented context.  But where this refers to earlier floats, it only refers to the *first* fragment of such earlier floats.  (I think... there's perhaps the interesting question of whether, given floats A and B within container C, if fragments A1 and B1 both fit within C1, and A2 can't fit at all within C2, is it allowable to fit B2 within C2?)
* The order of floats is a function of the order of their placeholders; the fragment number doesn't matter (or at least shouldn't; the Gecko code that actually does this is pretty sketchy in the presence of incremental relayout), so the third fragment of a float whose placeholder is earlier comes before the first fragment of a float whose placeholder is later.
* Only one fragment of a given float can be in a given fragment of its BFC (block formatting context); other than the above (or maybe there are other additions?) the float positioning rules refer to the fragments within the same fragment of the BFC.

GitHub Notification of comment by dbaron
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4434#issuecomment-545192895 using your GitHub account
Received on Tuesday, 22 October 2019 23:06:52 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:55 UTC