Closed
Bug 221510
Opened 21 years ago
Closed 21 years ago
percentage height quirk for tables doesn't work through form elements
Categories
(Core :: Layout: Tables, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: homaneag, Unassigned)
Details
Attachments
(1 file)
|
293 bytes,
text/html
|
Details |
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.1.4322)
Build Identifier: (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624
<table><tr><td valign=top>Top</td></tr><tr><td
valign=bottom>Bottom</td></tr></table>
should generate a page with the word Bottom at the bottom of the page.
<form><table><tr><td valign=top>Top</td></tr><tr><td
valign=bottom>Bottom</td></tr></table></form>
this won't do what is expected. The table is contained in the form and the
browser calculate the size of the form. Causing the word "Bottom" appears at
the upper half of the screen.
Both Mozilla and Mozilla Firebird has the problem
IE, Netscape 4.79 doesn't have this problem.
Because of this, most asp.net pages won't display correctly because they are
warpped in <form runat=server id=form1>
Reproducible: Always
Steps to Reproduce:
1.<form><table><tr><td valign=top>Top</td></tr><tr><td
valign=bottom>Bottom</td></tr></table></form>
2.
3.
Actual Results:
The word bottom appears at the upper half of the browser
Expected Results:
The word bottom should appear at the bottom
Could you attach an HTML testcase showing the problem? I suspect you meant to
say that the TABLE element had a height="100%" attribute.
Yes, the <table> has height=100%
<html>
<head
<title>Home Page</title></head>
<body>
<form>
<table width="100%" border="0" cellspacing="0" cellpadding="0" height="100%">
<tr>
<td valign="top" >Top
</td>
</tr>
<tr>
<td valign="bottom">Bottom</td>
</tr>
</table>
</form>
</body>
</html>
Summary: Form tag was considered as a visual component, causing valign to fail → percentage height quirk for tables doesn't work through form elements
this has been fixed by bz's checkin for the reflowstate bug 222730
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•