Huge Gap caused by <div> tags

Hi Everyone,

I have an unwanted gap at the bottom of my page which I cannot get rid of. I believe it is because of a <div> tag because if I remove all the <div> tags the gap disappears at the bottom only to be replaced by one at the top. I am new to html & CSS so a simple solution would be appreciated.

Here is the page http://www.snaptease.com/test.aspx

Many thanks in advance.

Martin

 

I can corect all that man... just remove that and if you cant do it,then PM me..

 

Sorry yovishnurulez I don't understand.

What do you suggest I remove?

Martin

 

I would try and remove the following from around line 410,

<td colspan="2" height="15">
      </td>

Code (markup):

I don't see what that is doing?


Also, for future reference this should probably just have been posted in the HTML section.

 

Hi Nicangeli,

Thanks for your suggestion, it didn't have any affect though I am afriad.

My apologies for posting in the wrong section.

 

I also strongly suggest you remove the margins and padding from everything in the page as well. I'm not at home so I can't give you a proper reset technique, but this quick and dirty trick will do the job nonetheless.

* {margin: 0; padding: 0;}

Code (markup):

Just put that at the top of your stylesheet. You WILL have to re-apply the margins and padding to those elements that you want to have these properties on, but it's a small price to pay for improved control.

 

Hi Dan,

Thanks for your help. But your suggestions had no affect on the gap or anything else on my site.

Can you suggest anything else?

Thanks in advance.

 

Well, cleaning up the 415 validation errors would be a good start - Looking at the layout even using tables there is NO reason for this to have more than ONE table, and even that could be avoided. You've got invalid markup, invalid CSS, nonsensical inlined presentation, and a whole host of other horrors that are pretty much biting you in the backside.

When it's not even valid HTML, one shouldn't be too surprised when it doesn't work someplace as you are relying on NOT correct code, but the correct handling of invalid code - something no two browsers even come close to doing. (Ok, not true, Opera and Safari both come close to each-other, there's a REASON they pass Acid2)