weird white space being introduced into <td>

  • Thread starter Thread starter neverstill
  • Start date Start date
N

neverstill

hi-

I have a table on a page there is 1 row and 2 cells
cell 1 has a user control that is basically just a DataList nested in a
table o fit's own.
then, below that user control I have some <p> tags to give me vertical
space, then after that I have an <asp:image> control.


Now, I just added the asp:image control. when I did, it put about 10-12
pixels of white space between this table and the header user control above
it. I only see this problem in Opera, Mozilla and Netsacpe, IE draws it
fine.

I know this is confusing, here is the basic code

<form id="Default" method="post" runat="server">
<uc1:Header id="Header1" runat="server"></uc1:Header>
<TABLE id="Table1" cellSpacing="0" cellPadding="0" width="780" border="0"
class="small">
<TR>
<TD width="150" vAlign="top">
<P>
<uc1:sideNavigation id="SideNavigation1"
runat="server"></uc1:sideNavigation></P>
<p>&nbsp;</p>
<p>&nbsp;</p>
<asp:Image id="Image_Testimonial" runat="server"
ImageUrl="~/Images/testimonial_01.gif"></asp:Image></TD>
<TD vAlign="top" width="4">
<asp:Image id="Image1" runat="server" ImageUrl="Images/Spacer_1x1.gif"
Width="10px"></asp:Image></TD>
<TD vAlign="top"><IMG src="Images/Spacer_1x1.gif" runat="server"
height="10"><br>
<asp:PlaceHolder id="placeholder_Main" runat="server"></asp:PlaceHolder>
</TD>
</TR>
</TABLE>
<P>
<uc1:Footer id="Footer1" runat="server"></uc1:Footer></P>
</form>




<uc1:Header is a table that is just a basic header user control.
The white space is appearing between "<uc1:Header" and "<TABLE id="Table1""

Only when the "<asp:Image id="Image_Testimonial"" is added.


Anyone have any idea what could cause this? I have seen this kind of thing
in the past where you need to have a </td> on teh SAME line as an <img> tag,
but I can't solve my problem this same way.

Thanks for any help!
Steve
 
problem solved. It was actually NOT what I thought it was... it turns out
that shabby testing combines with an orphaned <p> tag were the culprit!

thanks anyways!!
 
Back
Top