Description
Here is an interop issue between Chrome/Safari and Edge/Firefox:
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?