Hello and welcome to our community! Is this your first visit?
Register
Enjoy an ad free experience by logging in. Not a member yet? Register.
Results 1 to 8 of 8
  1. #1
    New Coder
    Join Date
    May 2009
    Posts
    10
    Thanks
    4
    Thanked 0 Times in 0 Posts

    Php & ie... Wtf?

    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.

  • #2
    Supreme Master coder! abduraooft's Avatar
    Join Date
    Mar 2007
    Location
    N/A
    Posts
    14,861
    Thanks
    160
    Thanked 2,223 Times in 2,210 Posts
    Blog Entries
    1
    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=ht...sher.com/blog/

    For example, you can't have a <div> or any other block level element inside a <p>
    The Dream is not what you see in sleep; Dream is the thing which doesn't let you sleep. --(Dr. APJ. Abdul Kalam)

  • Users who have thanked abduraooft for this post:

    titomuerte (02-24-2010)

  • #3
    God Emperor Fou-Lu's Avatar
    Join Date
    Sep 2002
    Location
    Saskatoon, Saskatchewan
    Posts
    16,994
    Thanks
    4
    Thanked 2,662 Times in 2,631 Posts
    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.
    PHP Code:
    header('HTTP/1.1 420 Enhance Your Calm'); 
    Been gone for a few months, and haven't programmed in that long of a time. Meh, I'll wing it ;)

  • #4
    New Coder
    Join Date
    May 2009
    Posts
    10
    Thanks
    4
    Thanked 0 Times in 0 Posts
    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....

  • #5
    Senior Coder
    Join Date
    Jul 2009
    Location
    South Yorkshire, England
    Posts
    2,318
    Thanks
    6
    Thanked 304 Times in 303 Posts
    Quote Originally Posted by titomuerte View Post
    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.

  • #6
    UE Antagonizer Fumigator's Avatar
    Join Date
    Dec 2005
    Location
    Utah, USA, Northwestern hemisphere, Earth, Solar System, Milky Way Galaxy, Alpha Quadrant
    Posts
    7,691
    Thanks
    42
    Thanked 637 Times in 625 Posts
    I saw this JS error in Firefox too:

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

  • Users who have thanked Fumigator for this post:

    titomuerte (02-24-2010)

  • #7
    New Coder
    Join Date
    May 2009
    Posts
    10
    Thanks
    4
    Thanked 0 Times in 0 Posts
    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.

  • #8
    Senior Coder
    Join Date
    Jul 2009
    Location
    South Yorkshire, England
    Posts
    2,318
    Thanks
    6
    Thanked 304 Times in 303 Posts
    Quote Originally Posted by titomuerte View Post
    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.
    Last edited by MattF; 02-24-2010 at 09:16 AM.


  •  

    Posting Permissions

    • You may not post new threads
    • You may not post replies
    • You may not post attachments
    • You may not edit your posts
    •