Bugzilla

(In reply to Mats Palmgren (:mats) from comment #7)
> Well, the codepen in comment 0 doesn't render as in the attached
> screenshot, neither in 65.0.1 nor in Nightly, so I don't know
> what to make of that..

I spoke to the reporter on Friday -- it looks like he made some edits to the live codepen in the time since filing the bug, while we tryied to sort out the best way to work around this compat issue -- and it seems that these updates inadvertently updated the testcase that'd he'd provided for this bug report.

(This is a good reason to avoid codepen for bug reports - testcases may change by accident and then cause confusion down the line.)

Anyway: here's his original testcase, if you're interested. The key thing that's present in the codepen now (& which avoids the bug is) `max-width:100%`, which (like `min-width:0`) works around the bug.

(In reply to Mats Palmgren (:mats) from comment #7)
> Well, the codepen in comment 0 doesn't render as in the attached
> screenshot, neither in 65.0.1 nor in Nightly, so I don't know
> what to make of that..

I spoke to the reporter on Friday -- it looks like he made some edits to the live codepen in the time since filing the bug, while we tryied to sort out the best way to work around this compat issue -- and it seems that these updates inadvertently made it into the testcase that'd he'd provided for this bug report.

(This is a good reason to avoid codepen for bug reports - testcases may change by accident and then cause confusion down the line.)

Anyway: here's his original testcase, if you're interested. The key thing that's present in the codepen now (& which avoids the bug is) `max-width:100%`, which (like `min-width:0`) works around the bug.