RetroZilla/layout/html/tests/table/bugs/bug5835.html

105 lines
2.0 KiB
HTML
Raw Normal View History

2015-10-21 05:03:22 +02:00
<HTML>
<BODY>
<p>This first table is the simple test case. Colspan confuses the width
allocation when there is an image in the colspanned row. </p>
<TABLE BORDER WIDTH="620">
<TR>
<TD WIDTH=420>
foo
</td>
<td WIDTH=200>
bar
</td>
</tr>
<TR>
<TD COLSPAN=2>
<img src="../images/rle.cgi?1865?111335577"
alt="Russian LinkExchange Banner Network" border="0" height="60"
width="468">
</TD>
</TR>
</table>
<p>This second table is the same as the first, minus the second
'colspan=2' row. Widths are now correct.</p>
<TABLE BORDER WIDTH="620">
<TR>
<TD WIDTH=420>
foo
</td>
<td WIDTH=200>
bar
</td>
</tr>
</table>
<p>An observation: Note that as the image-width approaches
the table-width, the two columns approach equal width (error increases).
Conversely, below some threshold image-width (which is about 390px or 30px less than the TD WIDTH=420), the error is (apparently) zero.
</p>
<p>Here the &lt;img width=600&gt;</p>
<TABLE BORDER WIDTH="620">
<TR>
<TD WIDTH=420>
foo
</td>
<td WIDTH=200>
bar
</td>
</tr>
<TR>
<TD COLSPAN=2>
<img src="../images/rle.cgi?1865?111335577"
alt="Russian LinkExchange Banner Network" border="0" height="60"
width="600">
</TD>
</TR>
</table>
<p>Here the &lt;img width=400&gt; (error is almost zero).</p>
<TABLE BORDER WIDTH="620" bgcolor="#dddddd">
<TR>
<TD WIDTH=420>
foo (single row table)
</td>
<td WIDTH=200>
bar (single row table)
</td>
</tr>
</table>
<TABLE BORDER WIDTH="620">
<TR>
<TD WIDTH=420>
foo
</td>
<td WIDTH=200>
bar
</td>
</tr>
<TR>
<TD COLSPAN=2>
<img src="../images/rle.cgi?1865?111335577"
alt="Russian LinkExchange Banner Network" border="0" height="60"
width="400">
</TD>
</TR>
</table>
<p>I tested the above with M4 and May01 build for win95. (The above
examples assume that images load normally -- N.B. for May01 the images
initially load, and the width error is visually apparent, but then the
images get replaced by their ALT text, and the width error is no
longer present -- this is, of course, a different issue/bug.)
</BODY></HTML>