-
Notifications
You must be signed in to change notification settings - Fork 707
Does a previously clear-ed float still contribute geometry? #2291
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
FWIW, depending on when/how the "geometry" of the previously cleared float is changed, chrome will respect or ignore the collision. View this behavior when adding/removing the |
If I copy the html and css from https://wptest.center/#/487ld5 and use them in jsfiddle or a local file, then Chrome behaves like Firefox and Edge. Is wptest.center doing something weird? @Nadya678 I get the same problem when not using
|
Locally I see that sometimes Chrome puts it on the left but after reloading puts it on the right. Likewise after resizing the wptest.center version a few times I see it ends up on the right. There seems to be some instability there. |
@birtles I can confirm that resizing the window on wptest.center sometimes yields to the float "moving" to the right. It seems like this is just a Chrome bug then. I filed https://bugs.chromium.org/p/chromium/issues/detail?id=811031 |
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:
That being said, we could clarify this particular case by answering the following question:
Does a previously clear-ed float still contribute geometry?
The text was updated successfully, but these errors were encountered: