...

View Full Version : Php & ie... Wtf?



titomuerte
02-23-2010, 06:51 AM
anybody care to weigh in on why Internet Explorer is struggling so badly with this page while Safari and Firefox are totally unaffected?! The W3 validator was....pretty much no help.

http://mischafisher.com/blog/

Best case scenario IE says "Finished, but with errors on page" other times it just totally fails to display anything below the header.

abduraooft
02-23-2010, 07:06 AM
The W3 validator was....pretty much no help. How could that be? There are a number of errors in your markup that can be easily fixed, see http://validator.w3.org/check?uri=http://mischafisher.com/blog/

For example, you can't have a <div> or any other block level element inside a <p>

Fou-Lu
02-23-2010, 03:06 PM
This is not an issue with PHP, rather an issue with Javascript from the sounds of it. I'll keep this here until it can be confirmed as an ongoing issue.

titomuerte
02-23-2010, 09:53 PM
I mean it's not useful because all sorts of sites have those small errors... google.com has 42 errors according to the validator....but clearly none of them are enough to hamper one's ability to correctly display google on any browser.

...but thanks! I'll look into the <div> issue and see if that's the culprit... stay tuned....

MattF
02-23-2010, 10:29 PM
I mean it's not useful because all sorts of sites have those small errors... google.com has 42 errors according to the validator....but clearly none of them are enough to hamper one's ability to correctly display google on any browser.

So in other words, you think that crap HTML code is excusable because 'other sites do it'? Simple fact. I.E can't even display perfect code properly for toffee, so what chance do you think it has with crap code? Clean up your HTML code, (and probably your javascript code too), and then see what difference it makes. If you're still having problems then, at least you will know it's not just due to invalid code which is causing it to take a nosedive.

Fumigator
02-23-2010, 11:01 PM
I saw this JS error in Firefox too:


Error: $("#default") is null
Source File: http://mischafisher.com/blog/wp-content/themes/jq/lib/js/fontResizer.js
Line: 3

titomuerte
02-24-2010, 07:33 AM
Well it's not that I don't care about crap code... it's that I'm a Congressional policy adviser by profession, a photographer by hobby, and - while I believe there is both truth and beauty and poetry in code - a part part part time student of Java and PHP.

So it's more about time cost/benefit than having flawless code.

But thanks for the help everyone.

MattF
02-24-2010, 09:11 AM
So it's more about time cost/benefit than having flawless code.

To put it in a manner you'll appreciate then, creating flawless code is a time/cost benefit. Do it correctly first time around, and you only end up doing it once. You have a page which is viewable, (not necessarily the same, but viewable), by any browser. Your page is forward compatible. You have code which doesn't make you keep wasting more time needlessly trying to figure out why things aren't working. As it is at the moment, all you have is a page which loads so badly as to make sure that at least 95% of visitors will never return to your site again, unless they have some masochistic streak.

Design right, design once. Simple as. Stick with your existing method and you'll still be sorting 'bugs' out years from now. The standards exist for good reason.



EZ Archive Ads Plugin for vBulletin Copyright 2006 Computer Help Forum