"ASSERTION: How did we end up with a negative min-size?" with flex and huge <video>

NEW
Unassigned

Status

()

defect
5 years ago
2 years ago

People

(Reporter: jruderman, Unassigned)

Tracking

(Blocks 1 bug, {assertion, testcase})

Trunk
x86_64
macOS
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments)

Reporter

Description

5 years ago
Posted file testcase
###!!! ASSERTION: How did we end up with a negative min-size?: 'aNewMinSize >= 0', file layout/generic/nsFlexContainerFrame.cpp, line 436

This assertion in UpdateMainMinSize was added in bug 1015474:
https://hg.mozilla.org/mozilla-central/rev/f5b98d327bde
Reporter

Comment 1

5 years ago
Posted file stack
Summary: "ASSERTION: How did we end up with a negative min-size?" with flex → "ASSERTION: How did we end up with a negative min-size?" with flex and huge <video>
See Also: → 1397449
You need to log in before you can comment on or make changes to this bug.