Closed Bug 281191 Opened 20 years ago Closed 20 years ago

Firefox renders an unwanted 5 pixel bottom margin to all images displayed in their default inline manner.

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

VERIFIED DUPLICATE of bug 22274

People

(Reporter: dan.clem, Assigned: bugzilla)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

In the example at http://www.danclem.com/firefox/firefox1.htm, there is an
unwanted 5 pixel gap below the image. It appears that images that are displayed
in the default inline manner have a built-in and unwanted 5 pixel bottom margin.
This occurs during Standards compliance mode only, not in Quirks mode.

Reproducible: Always

Steps to Reproduce:
1. Open http://www.danclem.com/firefox/firefox1.htm.
2. Or in general, put any image inside any container such as a DIV tag or a TD
table cell. Put a border around the container. You'll see an uncalled for 5
pixel bottom margin.

Actual Results:  
I got an unwanted margin beneath the pretty picture of my chili peppers.

Expected Results:  
I expected there to be no margin.
Duplicate of an invalid bug.

Read this article for explanation:
http://web.archive.org/web/20040202073255/http://devedge.netscape.com/viewsource/2002/img-table/

*** This bug has been marked as a duplicate of 22274 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
And please make sure to check the "Most Frequently Reported Bugs" list before
reporting a new bug, this is #1 on it.
Status: RESOLVED → VERIFIED
(In reply to comment #2)
> And please make sure to check the "Most Frequently Reported Bugs" list before
> reporting a new bug, this is #1 on it.

I spent a solid half hour looking through the bug list. Good thing it wasn't a
snake, 'cause it woulda bit me!

YOU GUYS ROCK! The link to Eric Meyer's page explained it perfectly.
You need to log in before you can comment on or make changes to this bug.