[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 576
  • Last Modified:

Looks good in FF, background image is off in IE


Please have a look at this in both IE and Firefox. It looks goof in FF, but is off in the bottom portion in IE. I can put up screenshots if you don't see it. FF 12.0, IE 9. Thanks!
3 Solutions
Dave BaldwinFixer of ProblemsCommented:
First you have an incomplete DOCTYPE.  I don't know where everyone gets this version but it's not complete and doesn't cause IE to work right.  Here are the correct versions:  http://www.w3.org/QA/2002/04/valid-dtd-list.html

Second, the code in lines 43 and 44 needs to be moved up into the <head> section.  It is not valid where it is.

Third, the <style> section starting at line 50 should also be moved in the <head> section.

And line 279 has an orphaned </p> tag which should be removed.

Fix those so we can see what it looks like.
HainKurtSr. System AnalystCommented:
remove font-family: georgia and see if it helps....
mel200Author Commented:
Ok, thanks, let me get back to you.
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

mel200Author Commented:
I took this to the man who is in charge of the sites, and he said this:
"The DOCTYPE is identical to the first one listed on that web page.  The orphaned </p> tag is valid - I've removed this.  It was in the footer though and had no bearing on the layout issues.

Although styles in the body are not strictly correct, all browsers have supported this for a long time now.  It makes the coding a little easier because blocks can be modularized (styles introduced along the way).  The other lines that he said were invalid are actually OK and have no bearing on this issue anyway.

I spent some time on this and found the problem.  It was caused by IEs handling of the dummy header graphic with the home page link.  I've added a parameter that suppresses the stock header HTML when using custom header HTML, as in this case.  All seems to be OK now on all browsers."

So now.... what do I do with this question? I'm happy to give points? What's your advice? Thanks.
Dave BaldwinFixer of ProblemsCommented:
I stand by what I said above.  If you think he knows better than I do, feel free to stick with him.  However, the W3C HTML Validator says the page has 46 errors and 75 warnings.  http://validator.w3.org/check?verbose=1&uri=http%3A%2F%2Fs61.funeralhomewebhosting.com%2F
Chris StanyonCommented:
I'm with Dave on this one. Your DOCTYPE is wrong, and it isn't identical to any DOCTYPE on that page. Yours is an incomplete HTML 4 Transitional. By looking at your code, you should be using an XHTML doctype - preferably STRICT.

You have this:

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">

It should be this:

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">

Change that and then run it through the validator. The single most effective way to get cross-browser compatibility is to use the 'standards' as they were meant to be used.
mel200Author Commented:
Thanks, guys- it's not that I think he knows better, but that I can't make changes to those parts of the pages. It's a template situation, and for this particular site we were making custom changes to the template.

What I'll do is issue points, because running it through the validator for cross-browser checking is the correct thing to do. meanwhile the issue seems to be fixed. Thanks for your help!
mel200Author Commented:
Thanks, everyone!
Dave BaldwinFixer of ProblemsCommented:
You're welcome.  Hope we gave you some ammunition for future problems.

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now