Closed Bug 205416 Opened 22 years ago Closed 22 years ago

Space after images when usning strict DTD in large table-structures (not with loose)

Categories

(Core :: Layout, defect)

Product:
Core
Component:
Layout
Platform:
x86
Windows 98
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 22274

People

(Reporter: lurq, Unassigned)

References

(
URL
)

Details

User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.4b) Gecko/20030507 Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.4b) Gecko/20030507 When using Strict DTD like (<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">) in large html/table structers images gets a space under them. The space is only horisontal and is affected by the font-size and line-height. If the line-height is set to zero the error wont appear. Exampel with strict DTD http://www.lurq.net/newbie/strict.html and with loose http://www.lurq.net/newbie/loose.html Reproducible: Sometimes Steps to Reproduce: 1. using Strict DTD 1. Creating a large table structure 2. Using CSS to control most of the height and width Actual Results: All images got a spaces under it, where ever the images is in the code. Expected Results: It should have no spaces like when you are using loose DTD. The DTD should affect the apperance, right?
Reporter, read also http://evolt.org/article/New_DOCTYPE_sniffing_in_upcoming_Mozilla_releases/1/32271/ and the links inside. What you want is the 'almost-standards'-mode, which is the same as the standards-mode, but which avoids the space after the image. It's not a bug btw, it's IE that is wrong. Workaround (if you can't change the doctype) add a style-attribute to your images like this : <IMG SRC="..." STYLE="display: block;"> *** This bug has been marked as a duplicate of 22274 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Product: Core → Core Graveyard
Component: Layout: Misc Code → Layout
Product: Core Graveyard → Core
You need to log in before you can comment on or make changes to this bug.