Announcement

Collapse
No announcement yet.

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

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • MRGTB
    replied
    Well has anybody noticed yet if you go into your styles in your admincp and view a template using Firefox. There is no SAVE option to click. Like you see it perfectly using IE.

    Dam funny, I spent ages try to save a template after editing it wondering what the hell was wrong, only to realise I was using my Firefox broswer (latest version). So I used the option to view the page in IE, and the template save option was there.

    Oh and I'm using the vB default template.
    Who ever said Firefox was the best. Naaaaaaaa!
    Last edited by MRGTB; Thu 15 Sep '05, 3:06am.

    Leave a comment:


  • Creepshow
    replied
    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.

    Leave a comment:


  • cbiweb
    replied
    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.

    Leave a comment:


  • Creepshow
    replied
    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??

    Leave a comment:


  • cbiweb
    replied
    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>
    Last edited by cbiweb; Fri 2 Sep '05, 6:52pm.

    Leave a comment:


  • Creepshow
    replied
    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...

    Leave a comment:


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

    Leave a comment:


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

    Thanks

    Leave a comment:


  • cbiweb
    replied
    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.

    Leave a comment:


  • Zachery
    replied
    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.

    Leave a comment:


  • cbiweb
    replied
    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.
    Last edited by cbiweb; Fri 2 Sep '05, 9:19am.

    Leave a comment:


  • Creepshow
    replied
    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?

    Leave a comment:


  • zlib
    replied
    why bother use a doctype then?

    Leave a comment:


  • Creepshow
    replied
    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.

    Leave a comment:


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

    Leave a comment:

widgetinstance 262 (Related Topics) skipped due to lack of content & hide_module_if_empty option.
Working...
X