Topic: help me with my table errors plz ;) (Page 1 of 1)

I don't know if this is the right thread, but I have a question regarding some html table/image problems that I am having.

Firstly, go here: www.forcefive.com/dsi1/header.html

Secondly, can someone please tell me why the orange buttons aren't lining up correctly. They are supposed to be right next to each other, and flush with the left side of the screen. Right now, they are like centered or something like that. They have spacing between them. ICKY! This is a rough draft version of a website I am doing, and I am trying to see what it will look like in a real browser. Thanks for the help in advance...

The poster has demanded we remove all his contributions, less he takes legal action.
We have done so.
Now Tyberius Prime expects him to start complaining that we removed his 'free speech' since this message will replace all of his posts, past and future.
Don't follow his example - seek real life help first.

"Shitzilla"? Mozilla is an excellent browser, does everything almost exactly as it should, and that's not even the full version. Netscape 4.x, on the other hand, you can call whatever you like.

The poster has demanded we remove all his contributions, less he takes legal action.
We have done so.
Now Tyberius Prime expects him to start complaining that we removed his 'free speech' since this message will replace all of his posts, past and future.
Don't follow his example - seek real life help first.

thanks a bunch, it works now. However, I do have one question. It seems that if I put ALL the img tags on one line, they line up right next to each other like they are supposed to. If i hit <enter> after one image, so that the next one goes to the next line in my editor (white space), there is a small space between the images..... why is this?

Slime, Mozilla shows promise, but it still has a long way to go. It's extremely slow, they are rewriting image library with every milestone release, no wonder why they call it libpr0n, and caching is still under heavy development as of 0.9 milestone, which has only level 1 cache implemented, while level 2 and level 3 still have to be implemented...

Acidbox, that's how it's supposed to be rendered (whitespace)...

Max,

I see what you are saying about the whitespace, but that doesn't make much sense. Why would the browser put a space between 2 images just from where the text is located in the .html file. I mean, it is supposed to only read html code, not the white space that I put in the file to make it easier to read (like when I hit <enter> after one image tag).

That's how HTML works. Any/all whitespace is rendered as one space. It's been that way since HTML 1.0 (Hell, maybe before).

Acidbox, as Linear said, that's how HTML works, so you can only complain to W3C... Anyway, if you *really* want to have each image tag on a separate line, you can write them like this:

<IMG SRC="bla1.gif" WIDTH="320" HEIGHT="240" BORDER="0"><IMG
SRC="bla2.gif WIDTH="320" HEIGHT="240" BORDER="0"><IMG
SRC="bla3.gif WIDTH="320" HEIGHT="240" BORDER="0"><IMG
SRC="bla4.gif WIDTH="320" HEIGHT="240" BORDER="0"><IMG
SRC="bla5.gif WIDTH="320" HEIGHT="240" BORDER="0">

See, acidbox, the thing is, how does HTML know you *don't* want a space between the images? It has to assume the newline is whitespace. If it didn't assume that, then this html code:

<p>Hello, my name is
Slime and this is my web page.</p>

would appear as

Hello, my name isSlime and this is my web page.

See the problem? So it has to assume that any new line (or tab, or any whitespace, you name it) is a space.

This is *not* true in cases like this:

<table>
<tr>
<td>text</td>
</tr>
</table>

whitespace between tags like the </td> and </tr> tags doesn't count. That's because you're not supposed to have text in that area anyway - it doesn't make sense to have white space there, so the browser knows that that whitespace is just for formatting your code, and doesn't put it into your page.

Thanks for the help guys, I really understand now . However, it seems to me that W3C should change that rule in the next HTML version. I mean, really, that is a hidden limiation. If I want a space, I will add an  nbsp, and if I want a break, I will add a <br>. I think it is pretty crappy that HTML decides when it *thinks* you want a space. Just my .02 cents. Thanks for the help though!



[This message has been edited by acidbox (edited 05-29-2001).]

Ok&amp;nbsp;then,&amp;nbsp;you&amp;nbsp;can&amp;nbsp;do&amp;nbsp;it&amp;nbsp;
that&amp;nbsp;way&amp;nbsp;if&amp;nbsp;you&amp;nbsp;like.&amp;nbsp;<br>=)

[This message has been edited by Slime (edited 05-30-2001).]

ROTFL, Slime.

Oh, that was a good one, and highly informative as well.

Acidbox, some concessions have to be made in any type of programming language (if you accept HTML as a programming language and a browser as the real-time compiler). It's especially difficult with HTML becuase the language was primarily developed to display text (among other things). This is a pain when compiling because the compiler needs to know what is text and what is code.

The whole whitespace thing was designed for just the reason Slime illustrated. So that you could type text and code tags without having to format everything single piece of whitespace. It's not exactly perfect as you pointed out, but it's the only solution available as of now and perhaps the forseeable future.

Well, I just wanted to give you a developers perspective on the thing. All computer languages have nuances like that. We just live with the limitations or we learn to use them.

Heh, sorry about the above sarcasm. Actually, one bad thing about using &amp;nbsp; for a space is that NBSP stands for "Non-Breaking SPace" - meaning that a line can't break on that space. I've used this once, when I had two words that looked better next to each other, and there was a line break between them, I put &amp;nbsp; between them to fix the problem. My point is, it's not something that should be used anywhere you want a space, because it could create some weird formatting in some cases.