Closed Bug 8676 Opened 25 years ago Closed 25 years ago

{compat} Adjacent floating images anomalously spaced on the vertical

Categories

(Core :: Layout, defect, P3)

x86
Windows 98
defect

Tracking

()

VERIFIED INVALID

People

(Reporter: Crysgem, Assigned: rickg)

References

()

Details

Attachments

(3 files)

Apprunner Build ID: 1999061908
**Alerting 3jrgm@qlink.queensu.ca and py8ieh=bugzilla@bath.ac.uk** Ye two, who have sat in the tumultuous lee of many similar-seeming bugs, may quickly assess this report's validity.
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?
*** Bug 8544 has been marked as a duplicate of this bug. ***
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.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → INVALID
Summary: Adjacent floating images anomalously spaced on the vertical → {compat} Adjacent floating images anomalously spaced on the vertical
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.
Status: RESOLVED → VERIFIED
Agreed. Marking as verified invalid.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: