Member Rara Avis
LOL - this is actually a good example of the differences between IE and Netscape. This screen looks perfectly fine in Netscape, but is a bit, uh, different in IE.
I've heard a ton of designers complain that NS sucks because it won't display their pages right. And they're not always real happy to hear the real problem isn't the browser, but rather sloppy coding. You see, Netscape insists that your HTML codes be right. If you start with a table tag, you have to end with a table tag. And if you don't, NS won't show ANY of your table.
IE, on the other hand, is far more forgiving. It tries to figure out what you meant to do. If you start with a table tag, then put in a bunch of rows and cells, IE will figure you just forgot the closing tag and do it for you. It will, in other words, still show the table, even though you never quite finished it. From a user's standpoint, that probably sounds pretty good - but it does encourage sloppy workmanship.
This is an example of IE trying to figure out what you meant to do and getting it very, very wrong. When you mentioned the < td > code in your paragraph (notice how I used spaces to make that tag not work), IE figured you wanted to start a new cell. Even though you never closed the tag, even though it doesn't match the column count in the rest of the table, IE tried its best to make it work.
Ya gotta love Gates...