Re: Frames still broke in NSN 3?

David Perrell wrote:
> 
> Stephanos Piperoglou notes:
> > > <TR>
> > > <TD><IMG SRC="image.gif" BORDER=0>
> > > <TD><IMG SRC="image.gif" BORDER=0></TD>
> > > </TABLE>
> >
> > This has whitespace (the newline) at the end of the first cell [2nd
> row]
> 
> Did you read my message? Why repeat the obvious?
> 
> The above as displayed in NSN 2.01:
> 
> *-------* *-------*
> |       | |       |
> | image | | image |
> |       | |       |
> *-------* *-------*
> |       | *-------*
> | image | |       |
> |       | | image |
> *-------* |       |
>           *-------*
> 
> > > <TR>
> > > <TD><IMG SRC="image.gif" BORDER=0></TD>
> > > <TD><IMG SRC="image.gif" BORDER=0>
> > > </TABLE>
> >
> > This has whitespace at the end of the second cell [2nd row]
> 
> It certainly does. And here is how it's displayed in NSN 2.01:
> 
> *-------*-------*
> |       |       |
> | image | image |
> |       |       |
> *-------*-------*
> *-------*       |
> |       | image |
> | image |       |
> |       *-------*
> *-------*
> 
> If you find this behavior logical, please share your insight.

For the vertical spacing, it _is_ logical. One cell has
an image and whitespace. It is rendered as the image, followed
by whitespace (*below* the image, perhaps due to fixed
width cells?). The other cell on the same row obviously
has to be of the same height. It only contains an image,
and that gets flushed to the bottom, leaving whitespace
on the top.

Now, can we go on with more serious matters in stead of
nitpicking over some pixels of whitespace in a device
independent environment?



Abigail

Received on Wednesday, 28 August 1996 11:52:33 UTC