IE/Firefox viewing problem

Discussion in 'HTML & Website Design' started by RboarderI, Feb 4, 2008.

  1. #1
    I am building a website in Dreamweaver and am having a viewing problem between IE and Firefox. I want the website to look as it does in Firefox, not the way it does in IE. In IE the right table is slid over too far and the whole page is not centered. Anyone have an idea on how to fix this problem...thanks in advance!!!


    Here is my site:
    www.guitarherogeek.com
     
    RboarderI, Feb 4, 2008 IP
  2. mds

    mds Active Member

    Messages:
    256
    Likes Received:
    7
    Best Answers:
    0
    Trophy Points:
    58
    #2
    Try to define the DOCTYPE first and then try to validate it so it can be all browser compliant

    Then check your tags again including your CSS
     
    mds, Feb 4, 2008 IP
  3. dextor_from_scriptlance

    dextor_from_scriptlance Peon

    Messages:
    26
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    0
    #3
    use DOCTYPE
     
  4. pipes

    pipes Prominent Member

    Messages:
    12,766
    Likes Received:
    958
    Best Answers:
    0
    Trophy Points:
    360
    #4
    In a nutshell is that what validate means, when it appears fine in all or most browsers?
     
    pipes, Feb 8, 2008 IP
  5. deathshadow

    deathshadow Acclaimed Member

    Messages:
    9,732
    Likes Received:
    1,999
    Best Answers:
    253
    Trophy Points:
    515
    #5
    No, the 'validator' is a program that makes sure that your HTML is VALID. The official W3C online one is here:
    http://validator.w3.org/
    Passing that means your HTML is actually HTML, VALID HTML. It means all your tags are opened and closed properly. If it doesn't pass that, well, OF COURSE IT'S NOT GOING TO WORK.

    Which right now on the page in question lists 39 errors, a hand count by me shows even more. The OP has invalid markup, by all accounts it shouldn't work at all ANYWHERE - the only reason it does is the error correction in browsers is making a feeble attempt at correcting it - the problem is browsers do NOT all handle the same errors the same way, making cross browser nigh impossible with invalid code without hacking it out the yazoo.

    The code - it's a train wreck - there is NO REASON to EVER use tables for a SINGLE td... if one only has content for one TD, that's what a DIV is for... I see multiple nested unclassed DIV's that don't seem to serve any purpose, most of those do not appear to be properly closed - NOT that one could tell with the willy-nilly nonsensical indenting. One thing that is quite certain is that if someone is resorting to this: <p>&nbsp;</p> to put spaces between paragraphs, they need to learn what a paragraph is (and what margins/padding are).

    As I say WAY too often of late - chuck it all and start over with clean semantic VALID markup, and separation of presentation from content.

    Of course, 99.999% of the problem likely lies right here:
    and it shows. BADLY.... and people wonder why I badmouth WYSIWYGS. The only thing you can learn from Dreamweaver, frontpage, or any of the rest of those steaming piles of crap is how NOT to design and code a website.
     
    deathshadow, Feb 8, 2008 IP
    pipes likes this.
  6. risoknop

    risoknop Peon

    Messages:
    914
    Likes Received:
    24
    Best Answers:
    0
    Trophy Points:
    0
    #6
    Agreed. When looking back to the past, when I knew nothing about coding websites, I'm glad I started to learn by typing in Notepad.

    All WYSIWYG apps are imho crap. Dreamviewer is the best from them but it's still crap.
     
    risoknop, Feb 8, 2008 IP
  7. Hakkairu

    Hakkairu Well-Known Member Affiliate Manager

    Messages:
    910
    Likes Received:
    24
    Best Answers:
    0
    Trophy Points:
    150
    #7
    Works good for me >_>
     
    Hakkairu, Feb 8, 2008 IP
  8. pipes

    pipes Prominent Member

    Messages:
    12,766
    Likes Received:
    958
    Best Answers:
    0
    Trophy Points:
    360
    #8
    deathshadow thanks for explaining, a very helpful post.
     
    pipes, Feb 9, 2008 IP
  9. RboarderI

    RboarderI Peon

    Messages:
    70
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    0
    #9
    Very helpful, thank you!
     
    RboarderI, Feb 22, 2008 IP
  10. innovati

    innovati Peon

    Messages:
    948
    Likes Received:
    63
    Best Answers:
    1
    Trophy Points:
    0
    #10
    the reason why there are IE issues is that Microsoft doesn't hold web standards in high regard and only maintains token compliancy with the standards.

    I would recommend you get Firefox (gecko rendering engine) Safari (webkit rendering engine), Opera (opera rendering engine) and IE (Trident rendering engine).

    There are other browsers out there, but they are either inconsequential or else are different interfaces for the same rendering engines as one of the above (Gecko powers: Firefox, camino, mozilla, netscape and galleon for example)

    Best of luck in the future. Long live gecko and webkit!
     
    innovati, Feb 22, 2008 IP