Open Bug 1058949 Opened 10 years ago Updated 2 years ago

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

Categories

(Core :: Layout, defect)

Product:
Core
Component:
Layout
Platform:
x86_64
macOS
Type:
defect

Tracking

()

People

(Reporter: jruderman, Unassigned)

References

Details

(Keywords: assertion, testcase)

Attachments

(2 files)

testcase
103 bytes, text/html
Details
stack
9.26 KB, text/plain
Details
Attached 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
Attached 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

    
  
Severity: normal → S3

          You need to log in
          before you can comment on or make changes to this bug.
        






  

    
  







  

    

      
Attachment

      

      
      
      
      
    

    

      

        

          

            
General

            

              Creator: 



            

            
Created: 

            
Updated: 

            
Size: