Closed Bug 195732 Opened 21 years ago Closed 21 years ago

Table height of 100% ignored when table inside a form

Categories

(Core :: Layout: Tables, defect)

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

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: oliver, Unassigned)

References

(
URL
)

Details

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.0.3705)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130

The example URL shows the incorrect behaviour and has a link to the same page 
with the form commented out in which case the page displays fine.

Reproducible: Always

Steps to Reproduce:
This is a duplicate
Whiteboard: DUPEME
Hmm, dupe of bug 10212?
*** Bug 204937 has been marked as a duplicate of this bug. ***
The table occupies the whole browser window, when the form element is styled
with height:100% . This may serve as a workaround for web page authors.
This might be a dupe of bug 41656. See the discussion at bug 113222.
*** Bug 215111 has been marked as a duplicate of this bug. ***
URL works fine (ie, table occupies the whole page) in mozilla1.0.2. this is a
regression 
For web page developers: 

  <form style="height:100%">

should only be used in Mozilla/Netscape. In some IE versions
we got strange results.
will this help confirm it ?
<html>
<head>
<title></title>
</head>
<body>
<!-- adding style="height: 100%" to FORM element fixes problem -->
<form>
<table width="100%" height="100%">
<tbody>
<tr>
<td width="100%" height="100%"> <iframe id="frame1_id"
width="100%" height="100%"
style="background: green none repeat scroll 0% 50%; -moz-background-clip: 
initial; -moz-background-origin: initial; -moz-background-inline-policy: 
initial;">
</iframe> <br>
</td>
</tr>
</tbody>
</table>
</form>
</body>
</html>


this works now as a result of the checkin for bug 222730
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
Whiteboard: DUPEME
You need to log in before you can comment on or make changes to this bug.