Closed
Bug 130669
Opened 23 years ago
Closed 23 years ago
Table Row/Cell heights are inexplicably expanding vertically.
Categories
(Core :: Layout: Tables, defect)
Tracking
()
People
(Reporter: michael, Assigned: karnaze)
References
()
Details
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Macintosh; U; PPC; en-US; rv:0.9.9) Gecko/20020311
BuildID: 2002031106
Table Row/Cell heights are inexplicably expanding vertically. This dose not
happen in released versions of Netscape 6, Netscape 4.7 or IE 5+
Reproducible: Always
Steps to Reproduce:
1. Load a page with table cell and row heights that you expect to be 1 pixel high.
2.
3.
Actual Results: Table Row/Cell heights are inexplicably expand vertically.
Expected Results: Render the table cells/rows 1 pixel high.
Comment 1•23 years ago
|
||
Sure it does not render like IE5.5 (but it does not mean that
Mozilla is not correct since I notice this site triggers the
strict mode).
Assigning to the right component (I hope) -->HTML tables
Component: XP Apps → HTMLTables
Comment 2•23 years ago
|
||
Seeing that on NT4, and changing Assigned to
Assignee: trudelle → karnaze
QA Contact: paw → amar
Reporter | ||
Comment 3•23 years ago
|
||
>>Sure it does not render like IE5.5
Well, I was more surprised that Mozzila isn't rendering like earlier versions
(i.e. Netscape 6). I was merely making the point of what was expected as
a "correct" rendering of said page.
>(but it does not mean that Mozilla is not correct since I notice this site
>triggers the strict mode).
What is the "strict mode" you refer to and how is it triggered? The doctype
on all pages is:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/1999/REC-html401-19991224/loose.dtd">
Comment 4•23 years ago
|
||
See http://www.mozilla.org/docs/web-developer/quirks/ which explains Mozilla's
two rendering modes.
See http://www.mozilla.org/docs/web-developer/quirks/doctypes.html which
explains the doctype thing in great detail.
The reason Netscape 6 rendered this differently is because it had a bug in how
it parsed doctypes.... this bug is no fixed.
Finally, see bug 22274 for a detailed discussion of this problem along with the
CSS you want to apply to your page to make it render the way you want. It's a
longish read, but it's worth it.
The current rendering is correct for a page in strict/standards mode....
*** This bug has been marked as a duplicate of 22274 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•