653478 - too-wide table does not clear right float

Status: RESOLVED DUPLICATE of bug 478834

(Core :: Layout: Floats, defect)

Description

[altieres]

User-Agent:       Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0) Gecko/20100101 Firefox/4.0
Build Identifier: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0) Gecko/20100101 Firefox/4.0

I have two divs, one above the other, I tried put somes <br> between them, but the one below is drawed above ,when I put a space between them so everything goes fine. Its a local page, I don't know how to send the page to you...
there is a way that I can send a file, so I can save the page, zip and send... It will be easier to understando with the example..

Reproducible: Always

Steps to Reproduce:
1.Remove the space and you will see It happen
2.Put the space again and everything goes fine
3.


Expected Results:  
the space should not make any difference in the page. 

please, look at the attachment

Comment 1

[Matthias Versen [:Matti]]

Attach a minimal testcase using the "add an attachment" link above.
minimal = html file with the tags that are required to reproduce the problem and nothing more.

Comment 2

[altieres]

Attachment: try find the comment "REMOVE THIS SPACE AND YOU WILL SEE THE BUG""

the test-case

Comment 3

[j.j.]

Attachment: reduced testcase

Comment 4

[j.j.]

Green box should be overlapped. Works in Fx3.6, but not an HTML5 parser issue.

Comment 5

[Boris Zbarsky [:bzbarsky]]

Attachment: Testcase that's actually pretty reduced

Comment 6

[Boris Zbarsky [:bzbarsky]]

This last testcase shows that the underlying bug (which may be a duplicate) is present in 3.6 as well.  It's just that the handling of the <div style="display:inline"> is broken in Gecko 1.9.2, so that the <br>s end up being able to clear the float or something weird.  But in Gecko 2 we fixed block-inside-inline handling to follow the spec.

In any case, the bug is that the table is overlapping the float instead of clearing it.  David, do we have an existing bug on that?

Comment 7

[altieres]

Hi,
I think that someone should work in this bug, It is a little old.
I am a newbie but I accept suggestions about what I can do to help solve this bug, and I think that the status should be changed, this bug is not UNCONFIRMED.
and still happens in firefox 6.0...

Regards

Altieres

Comment 8

[j.j.]

Altieres, changing the Status doesn't necessarily trigger any action here. 

Anyway, 
> David, do we have an existing bug on that?
I'm not David but i don't know one.

Someone should give this bug a more meaningful title.

Comment 9

[altieres]

>> Altieres, changing the Status doesn't necessarily trigger any action here. 

I know that doesn't trigger any action, but someone that dont know that bug, now will see that it is a new one, I change the title for one more meaningful.
I hope this help.

Comment 10

[Boris Zbarsky [:bzbarsky]]

> I'm not David but i don't know one.

I cced a particular David on the bug when I asked the question, if you note.

Comment 11

[j.j.]

(In reply to Boris Zbarsky (:bz) from comment #10)
> > I'm not David but i don't know one.
> 
> I cced a particular David on the bug when I asked the question, if you note.

Sure, I know which David. I don't know an existing bug.
(recently at the job center I claimed my English was "business fluent" but that's an obvious lie)

Comment 12

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

Probably the part of bug 25888 that should get split out to cover blocks?

Comment 13

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

(Though I think there are other bugs covering the fact that we're hitting that when the float and the block are exactly even vertically, which I think may be a problem not as old as the original.  Either way, adding a <div style="height: 1px"></div> between the div and the table makes the problem go away, which shows that it is at least related to bug 25888 for blocks.)

I should probably go get separate bugs filed on the followup bits there and close the existing bug.

Comment 14

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

Fixed by bug 478834.