Closed Bug 1686409 Opened 5 years ago Closed 3 years ago

floats inside of a multicol do not balance properly over the columns

Categories

(Core :: Layout: Columns, defect)

Firefox 84
defect

Tracking

()

RESOLVED DUPLICATE of bug 1695509

People

(Reporter: fvanderwielen, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:84.0) Gecko/20100101 Firefox/84.0

Steps to reproduce:

go to https://codepen.io/fvanderwielen/pen/JjRmmeg

Actual results:

the columns are not balanced out upon initial page load: only one div is in the second column, and the other divs are in the first column

Expected results:

both columns should balance out, it's the USP of multicol :)

what is interesting is that after opening devtools the columns do balance out, seems/feels like the reflow triggered because of the change of width.

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Component: Untriaged → Layout: Columns
Product: Firefox → Core

Thanks for reporting, and for the clear testcase. Yes, this is definitely broken on initial reflow. It seems to resolve itself for me if I resize the window, or trigger a full reflow in other ways such as zooming the content.

(FWIW, I saw some variations on the exact nature of the brokenness, e.g. by changing the column count to 3, and by removing and then restoring the float property. At one point in the 3-col version, sections 5 and 6 both appeared at the top of the 3rd column, overprinting each other. Definitely quite flaky.)

Severity: -- → S3
Status: UNCONFIRMED → NEW
Ever confirmed: true

Firefox shows the expected results now. mozregrssion finds this range https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=578715b6d3fcb21c0b61996347260ef9b119d0d2&tochange=8508c35e49793fbe402ad2a706a57fabd1c2b0c4

I guess bug 1695509 fixed this since it is related to float elements in a fragmentation environment.

Status: NEW → RESOLVED
Closed: 3 years ago
Duplicate of bug: 1695509
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.