SitePoint Sponsor

User Tag List

Results 1 to 2 of 2
  1. #1
    The Legend Indian's Avatar
    Join Date
    Nov 2001
    Location
    Gods' Own Country
    Posts
    890
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Dual CSS rendering engines in IE6

    This is from an article by Tom Dahm(COO, NetMechanic Inc.)
    Of all the changes to IE 6, perhaps the most important for Webmasters is the addition of dual CSS rendering engines. While this new feature helps Internet Explorer comply with the W3C HTML standards, it may also break your existing Web pages.
    ....
    The new rendering engine changes the rules for writing style sheets so that some things that were permitted in the past are now illegal.

    ....IE 6 uses the DOCTYPE tag to decide which rendering engine to use. If your page doesn't use a DOCTYPE, then IE 6 will use its classic engine. Also, if you use a DOCTYPE that includes the words "Transitional," then IE 6 will usually use the classic engine. :

    <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">

    However, if your DOCTYPE tag includes the words "Transitional" and gives a URL where the DTD can be found, then IE 6 will instead switch to the new rendering engine. So this version of the tag will use the new engine:

    <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"
    "http://www.w3.org/TR/html4/loose.dtd">

    Likewise, if your DOCTYPE doesn't include the word "Transitional" or includes the word "Strict," then IE 6 will use the new rendering engine. So either of these DOCTYPE tags will trigger the new rendering engine:

    <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">

    <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Strict//EN">
    Indian

  2. #2
    SitePoint Wizard Ian Glass's Avatar
    Join Date
    Oct 2001
    Location
    Beyond yonder
    Posts
    2,384
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Good info. Thanks, Indian! I've known for a while that IE5 for the Mac and NS6 renders pages differently depending on the doctype.

    Unfortunately, I don't think this approach helps compel designers to support standards. If anything it does the opposite. When a designer's old tactics and methods still "work," then they have little reason to improve them. It's the "if it ain't broke, don't fix it" mentality -- unfortunately, the 4.0 method of doing things is broken for so many people in so many ways.

    So, how do you go about supporting standards? By unilaterally rejecting old and obsolete ways of doing things, in my opinion. I don't think I'll get my wish any time soon, maybe in version 7.

    ~~That's My 2


Bookmarks

Posting Permissions

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