CSS layout

[web-content-king]

OK, forgive me if this innappropriate, and let me know if I should post elsewhere, but does anyone know why the bottom footer of your page layout might ride up the page in a pure CSS layout?

Could anyone take a quick look at my new page and see if they have any ideas? (note: there's a table in the middle, which I put there when working on this on the fly, but that isn't what's causing the problem)

http://upmarketcontent.com/demo/

I've tried everything...it was h*ll just to get the top to work in all browsers...IE was of course the big culprit, but then Opera got very finnicky with the workarounds we had to use for IE.

Second question: do you think the footer looks bad?

[ADAM Web Design]

You've got a space or a piece of code or something at the bottom of the page that reveals itself when you do a "Select All". I can't see what it is per se, but I can see some things it might be.

Did you try getting rid of that stats counter? I would guess that it's your problem since it falls outside of your Page div.

Also, you should have all of your attributes closed in quotes and using lower case. That probably isn't it, but it's just good coding practice.

You've also got some other JScript errors that may be contributing to your problems.

Normally I wouldn't point this out, but since it's your business, you do have a typo in the following paragraph:

"Show me how my business's content can make more money. email me the twice-monthly UpMarket Content TipSheet."

"Email" should be capitalized. It's the one just above the footer, not the one in the top left.

[drummin]

More than likely it is one of these problems that is throwing things off.

[Error] Line (104): Required attribute "type" not found within tag <input>
[Error] Line (106): Required attribute "type" not found within tag <input>
[Error] Line (107): Required attribute "type" not found within tag <input>
[Error] Line (110): Required attribute "type" not found within tag <input>
[Error] Line (112): Required attribute "type" not found within tag <input>
[Error] Line (155): Required attribute "type" not found within tag <input>
[Error] Line (183): Required end tag </span> not found
[Warning] Line (49): End tag </p> without start tag
[Warning] Line (61): End tag </p> without start tag
[Warning] Line (122): End tag </p> without start tag
[Warning] Line (182): End tag </p> without start tag
[Warning] Line (192): Illegal symbol / within tag

[web-content-king]

Originally Posted by ADAMWebDesign

Also, you should have all of your attributes closed in quotes and using lower case.

You mean the CSS attributes? Shoot. I thought I had that one taken care of...do you remember where those problems were? In the page body or in the columns and other layout items? If it's the page body itself it might be some old code that escaped the revamp, when I copied and pasted content from the old to the new. You see where doing something wrong once in the past creates problems down the line even when you change your ways.

Originally Posted by ADAMWebDesign

Normally I wouldn't point this out, but since it's your business, you do have a typo in the following paragraph:

"Show me how my business's content can make more money. email me the twice-monthly UpMarket Content TipSheet."

"Email" should be capitalized. It's the one just above the footer, not the one in the top left.

Thank you for pointing that out. You SHOULD point stuff like that out normally; it is something that affects the credibility of the site in the minds of many visitors no matter the market sector of the website. Plus, many people spell and write about as well as I code, so pointing out those errors really is as helpful as pointing out coding errors; more really, since the code errors don't normally affect the appearance of the website while you can't hide the typos.

My vanity forces me to say that this is just a staging page, not one that's linked to anywhere on the current page; it hasn't been copyedited. The error arose during a find and replace that apparantly wasn't case-sensitive.

I wish this thing had spell-check; I'm a little self-conshuss now. :)

[drummin]

<table border=0 align="ccenter" cellspacing=10 align="top" width=400>

Extra "c" in align and not quoted in some of the other attributes.

[web-content-king]

I think I got it. It's so simple, I could cry, but I don't think it's the "validating" solution. Still, it looked good on every browser on browsercam.com

I just set a value for the height of the left-most box. It doesn't matter what the actual height is, the footer follows it.

I fixed all the actual validation errors just for the sake of it (quotes missing etc. I didn't fix since I will be updating the page content soon anyway). Did not affect the appearance one bit, as you would expect with validation errors. But I did discover one problem in my CRM that was causing a semi-important javascript no script to be ruined, so I gained that.

thanks for all your help.

[Faglork]

Originally Posted by web-content-king

Did not affect the appearance one bit, as you would expect with validation errors.

[Warning] Line (49): End tag </p> without start tag
[Warning] Line (61): End tag </p> without start tag
[Warning] Line (122): End tag </p> without start tag
[Warning] Line (182): End tag </p> without start tag

will in most cases have all sorts of strange side effects, especially in connection with <form>

Validation is NOT for visual appearance, BTW. However, if you do have problems, it is usually best to fix the obvious errors first, because you never know what kind of side effects you get. I've seen a lot of mysterious things which went away by simply validating the code.

On a completely different level: If you name yourself "Website Content Provider", at least the content should be error-free, don't you think? Otherwise, you give your competition a head start by letting them point out that you even don't care about simple HTML issues.

Since validation is really no big deal, I would do it habitually.

Alex

[Webnauts]

There are 80 errors and 23 other minor issues which must be fixed. And that in concerns of SEO, browsers compatibility, etc.