W3C home > Mailing lists > Public > public-css-archive@w3.org > February 2018

[csswg-drafts] Does a previously clear-ed float still contribute geometry?

From: François REMY via GitHub <sysbot+gh@w3.org>
Date: Thu, 08 Feb 2018 19:42:12 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-295640688-1518118930-sysbot+gh@w3.org>
FremyCompany has just created a new issue for https://github.com/w3c/csswg-drafts:

== Does a previously clear-ed float still contribute geometry? ==
Here is an interop issue between Chrome/Safari and Edge/Firefox:
> https://wptest.center/#/487ld5
> ![image](https://user-images.githubusercontent.com/364405/35994201-90968bba-0cc4-11e8-971d-06b2bd93d5aa.png)
> ![image](https://user-images.githubusercontent.com/364405/35994266-bfadca6c-0cc4-11e8-9ff6-19da68946602.png)


In the testcase, a float is colliding another float that has already been cleared but reappear in the constraint space due to a negative margin set in the flow. Chrome/Safari ignores that collision, while Firefox/Edge honor it.
 
I don't think there is a relevant text to clarify the expected behavior here since:

> In CSS 2.1, if, within the block formatting context, there is an in-flow negative vertical margin such that the float's position is above the position it would be at were all such negative margins set to zero, the position of the float is undefined. 
> www.w3.org/TR/CSS2/visuren.html#float-position

That being said, we could clarify this particular case by answering the following question:

**Does a previously clear-ed float still contribute geometry?**


Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2291 using your GitHub account
Received on Thursday, 8 February 2018 19:42:45 UTC

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