Closed Bug 177164 Opened 23 years ago Closed 23 years ago

Unintended spaces under images are displayed by Mozilla (XHTML)

Categories

(Core :: XML, defect)

x86
All
defect
Not set
normal

Tracking

()

VERIFIED WONTFIX

People

(Reporter: asr, Assigned: hjtoi-bugzilla)

References

()

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020913 Debian/1.1-1 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020913 Debian/1.1-1 Mozilla insists on showing some spaces below images in '<td>'s even though they are nowhere defined. This is a problem that only occurs in Mozilla, in both Netscape, Konqueror and Internet Explorer you can workaround the problem by adding '<br />' after the '<img>' tag. Both XHTML(1.1) and CSS are validated. PS. I hope this is the right category. Reproducible: Always Steps to Reproduce: Expected Results: Mozilla should simply display the layout without unintended spaces.
It's actually normal. For an explanation, read http://evolt.org/article/New_DOCTYPE_sniffing_in_upcoming_Mozilla_releases/1/32271/ and especially http://devedge.netscape.com/viewsource/2002/img-table/ . It's caused by an inconsistency in the CSS2 standard, and only Mozilla tries to follow the standard to the letter. It's the reason why Mozilla implements an "almost-standards-mode", which is the same as "standards mode" plus a workaround for this problem. When CSS3 is finished, it might contain a fix for this. Workaround : use a style="display:block" on every image. Or try to use the "almost standards mode", for example by using XHTML-Transitional.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → WONTFIX
Anders, you have PLENTY of spaces defined in your code. If you wanted to avoid spacesm you would use <td><img .........></td>. Remember that newline character ALSO is a whtespace character! For that approach taken to the extreme, see the HTML code of http://wesha.lib.ru That site contains no single unwanted space. v.
Status: RESOLVED → VERIFIED
Jo Hermans: Thank you for a very quick also very useful answer! Wesha: Actually I thought that this matter was obsolete. It doesn't seem to make a difference since XHTML, which suits me very good indeed.
You need to log in before you can comment on or make changes to this bug.