These spaces...

[alexjewell]

I'm doing a school project and I decided to create a website for it. Here's the url: http://flamehtmlstudios.com/max/

Now, for some reason, spaces are showing up before and after the content. Can someone figure out why?

[QuickScriptz]

I am not sure what you mean - all appears fine for me in IE 6.

[alexjewell]

The problem is in Firefox

[QuickScriptz]

I am not very proficient with tables and slices and etc. but the problem your experiencing might have something to do with the fact that you close your <table> tags and both your <div> before you start your content.....

As for Firefox - its a great browser for usability and all but it sure makes a webmasters job 10x more difficult - i hate it!

Good Luck With Your Problem!

[alexjewell]

Alright, noticed I was closing the container tag. I got rid of the extra </div>. The tables in this case are simply to organize the navbar(s) and not the layout. The layout is basically div's.
It's still got the spaces
:/

[ItsMeOnly]

As for Firefox - its a great browser for usability and all but it sure makes a webmasters job 10x more difficult - i hate it!
Yeah, nothing beats IEs: "object has no properties", not even the error console, and DOM inspector? don't even think about it...

[Twey]

There is no tabular data on that page. There shouldn't be any <table>s on it either. You've used an odd form of pseudo-XHTML. Please, stick to HTML (http://www.hixie.ch/advocacy/xhtml). Your page also doesn't validate (http://validator.w3.org/check?uri=http://flamehtmlstudios.com/max/), meaning that it's going to appear quite differently in most browsers, since Quirks mode is very unpredictable.
As for Firefox - its a great browser for usability and all but it sure makes a webmasters job 10x more difficult - i hate it!By following standards (to a far greater extent than IE, anyway), it makes a webmaster's job one heck of a lot easier if s/he's any good and doesn't rely on one of IE's many bugs. If said webmaster has relied on one of these bugs, the page will display incorrectly in any browser except IE (and probably any version of IE except the one in which it was developed) anyway, and there's no point in blaming what is merely one of those browsers for his/her bad design decisions. The page in question on this thread, for example, displays this problem in Firefox, Konqueror, and Opera, to name but three.

[mwinter]

Your page also doesn't validate, meaning that it's going to appear quite differently in most browsers, since Quirks mode is very unpredictable.

Validity doesn't trigger either "Quirks" or "Standards" mode rendering: the document type declaration does. However, invalid markup will cause browsers to perform error correction which may cause the document tree to be constructed differently. This latter issue can affect both what a script will encounter when traversing the document tree, and possibly form submission and rendering behaviour as elements may be nested differently than intended.

Mike