8676 - {compat} Adjacent floating images anomalously spaced on the vertical

Status: VERIFIED INVALID

(Core :: Layout, defect, P3)

Description

[Crysgem]

Apprunner Build ID: 1999061908

Comment 1

[Crysgem]

Attachment: Note the spacing of each pair of article images

Comment 2

[Crysgem]

**Alerting [e-mail] and py8ieh=[e-mail]**
Ye two, who have sat in the tumultuous lee of many similar-seeming bugs, may
quickly assess this report's validity.

Comment 3

[John Morrison]

Well, here's a test case. Nav4.x and 5.0 have different views of dealing with
the flow into a fixed width block or table (and I don't know which is correct
 -- must go read a bit  ;). Perhaps this is a dup -- py8ieh?

Comment 4

[John Morrison]

Attachment: testcase; flowing a second image into a fixed width block or table

Comment 5

[John Morrison]

*** Bug 8544 has been marked as a duplicate of this bug. ***

Comment 6

[John Morrison]

Attachment: testcase; based on bug 8544 -- a variation of the previous attachment to bug 8676

Comment 7

[John Morrison]

The most recent attachment includes comments explaining the tests (modulo
bonehead proofreading failures). In this test, the behaviour is the same for
tables, but notably 'odd' for the fixed-width divs.

Comment 8

[Hixie (not reading bugmail)]

All behaviour in all test cases in this bug is per the CSS specs.

 1. Images are equivalent to text in these cases (display:inline), so, like
    text, they should flow to the next line if the container is not wide enough
    to hold them.
 2. A floated image should not affect the parent's borders, so the border in
    the third test case is correct.
 3. If you set the border, padding and margins of the tables to 0, you get the
    same behaviour in cells as in DIVs. In some of the tests, the cell width
    is less than the DIV width, so a direct comparison is incorrect.

Marking bug INVALID.

Comment 9

[Chris Petersen]

Agreed. Marking as verified invalid.