Announcement

**Zachery** · Fri 2 Sep '05, 6:22am

http://validator.w3.org/check?uri=ht...ng-freeks.com/ Start by fixing the invalid xhtml your using.

**Creepshow** · Fri 2 Sep '05, 6:26am

Originally posted by Zachery

http://validator.w3.org/check?uri=ht...ng-freeks.com/ Start by fixing the invalid xhtml your using.

Thanks Zach, but I dont think that's the problem. Because when I say enter www.rajah.com, it comes up with LOADS of 'invalid' errors, but still looks fine in all browsers.

Why would this be?

Thanks very much, appreciate your help.

**zlib** · Fri 2 Sep '05, 6:27am

why bother use a doctype then?

**Creepshow** · Fri 2 Sep '05, 6:44am

Originally posted by zlib

why bother use a doctype then?

With all due respect this isn't what I'm asking.

My question is simply why is my site showing up incorrectly in alternative browsers when other sites with failed validation errors show up fine?

**cbiweb** · Fri 2 Sep '05, 9:15am

I hate to say this because I hated hearing it when it was said to me once upon a time. But I've become a better designer after listening to the advice:

Your site is showing correctly in the other browsers; that is, they are parsing your code exactly as the code is written. IE is making up for your invalid code by extrapolating what it thinks you meant to do, and displaying it accordingly. As good a job as Ie does with this, it is still not a good way to design a site.

If you would just go ahead and validate your code, and fix it, you will see your site work fine in Firefox and other browsers. It might then look broken in IE, because IE still does not understand valid code. So you will have to apply fixes and workarounds for IE only. Yes, that's the way it is. You can argue, but it doesn't change the facts. People might jump in here and dispute what I've said, but first-hand experience, and helping others straighten out their sites the same way over and over again has proven my point.

Try it, you'll like.

btw, www.rajah.com might look fine in other browsers, but not all invalid code effects a browser the same way. The errors there obviously are not affecting other browsers the way your code does. That's why fixing all errors will be a big help in fixing the site.

**Zachery** · Fri 2 Sep '05, 9:17am

If you would just go ahead and validate your code, and fix it, you will see your site work fine in Firefox and other browsers. It might then look broken in IE, because IE still does not understand valid code. So you will have to apply fixes and workarounds for IE only. Yes, that's the way it is. You can argue, but it doesn't change the facts. People might jump in here and dispute what I've said, but first-hand experience, and helping others straighten out their sites the same way over and over again has proven my point.

Thats just not true, IE is a preferctly suiteable XHTML browser, and it renders content correctly alot of the time, save for some of the nastier div/css bugs. Its not hard to break firefox. Firefox doesn't render everything prefectly, and neither does IE they both have their problems.

But, a good start is always valid code, if your entire document is xhtml valid then all browsers should render it right. Just because it doesn';t look the same doesn't mean either browser is broken.

**cbiweb** · Fri 2 Sep '05, 9:25am

Originally posted by Zachery

...Its not hard to break firefox. Firefox doesn't render everything prefectly...

I've never had a problem with the way Firefox displays pages that I code. I've had many problems with how IE does it. The culprit is always IE's lack of support for certain aspects of CSS. But there are workarounds for all that, anyway.

**Creepshow** · Fri 2 Sep '05, 12:21pm

So anyone know exactly what I have done wrong in my code?
What is it exactly I need to change?

Thanks

**cbiweb** · Fri 2 Sep '05, 2:49pm

Have you run your code through the W3C validator? Why don't you do that? It will reveal many magical things.

**Creepshow** · Fri 2 Sep '05, 4:08pm

Originally posted by cbiweb

Have you run your code through the W3C validator? Why don't you do that? It will reveal many magical things.

I have done that yes, but a lot of the 'errors' it finds are things that I need in order for the site to function correctly. I dont really understand the W3C Validator thing to be honest, are you sure it's completely accurate? I mean I wouldn't want to mess up the work I've done on my site so far...

**cbiweb** · Fri 2 Sep '05, 6:47pm

I just ran your code through the validator, and saw many many errors that need to be fixed. Unclosed <p>'s, invalid <br>'s, and the closing </body> tag is missing altogether. Not to mention you have upper case and mixed case tags that are invalid in XHTML. Fix all the errors that you can, and then see how your site looks in other browsers.

<edit>
Oh, just noticed that you have the opening <body> tag placed about 60 lines down from where it should be. What's up with that?
</edit>

**Creepshow** · Sat 3 Sep '05, 2:45pm

Nevermind, sorted it out now.

PS. This is weird, I'm typing & it's come up in the times roman font for some reason. Anyone know why??

**cbiweb** · Sat 3 Sep '05, 5:08pm

For me it's Times New Roman and red! And the background of the message editor is #E1E1E2, which is a shade of gray, but I don't think it was that color before, either.

**Creepshow** · Sat 3 Sep '05, 6:37pm

Originally posted by cbiweb

For me it's Times New Roman and red! And the background of the message editor is #E1E1E2, which is a shade of gray, but I don't think it was that color before, either.

The background is grey for me too. It's weird.

Announcement

Fine in IE, but other browsers mess up. Help please!!

Fine in IE, but other browsers mess up. Help please!!

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment