How to Design a CSS Web Site for Both Firefox and Internet Explorer - The Diigo Meta page

• 08 Apr 10
  

  robidigital

  webdesign browsercompatibility

• 27 Sep 09
  

  Ameeno

  The placement of this line of CSS is important if my page is still to look good in Firefox and Safari. The IE line needs to come first. Firefox and Safari will read that line and then it will be over-ridden by the body > div#nav selector lower in the document. IE 6 will read the first line and set the styles. It will then ignore the child selector, as it doesn't recognize them. When IE 7 comes along, it will act like Firefox and Safari.

  CSS HACK css webdesign

• 19 Jul 09
  

  henk jurriens

  css firefox IE

• 03 Apr 09
  

  Charith Rodrigo

  From Internet Explorer Ebooks CSS

• 12 Dec 08
  

  Powmow

  • Hiding Styles from IE 6

     

    It's actually really easy to hide styles from IE 6 but make them visible to standards compliant browsers. Use child selectors. 

    In one design I built, I created a two column layout that required margins and padding. This meant that I was hitting the box model differences when I viewed the page in IE 6. My first CSS style sheet for Firefox included a line like this: 

    div#nav { width: 150px; margin-left: 20px; }

     

    This made the page line up perfectly in Firefox and Safari, but in IE the nav column was pushed over to the right too far. 

    So, I converted the line to use child selectors. The #nav div is a child of the body tag, so I changed the line to read: 

    body > div#nav { width: 150px; margin-left: 20px; }

     

    Of course, doing this made the #nav div lose all it's properties in IE, so I needed to add in some IE styles to get IE 6 looking okay. I added this line to the CSS: 

    #nav { width: 150px; margin-left: 10px; }

     

    The placement of this line of CSS is important if my page is still to look good in Firefox and Safari. The IE line needs to come first. Firefox and Safari will read that line and then it will be over-ridden by the body > div#nav selector lower in the document. IE 6 will read the first line and set the styles. It will then ignore the child selector, as it doesn't recognize them. When IE 7 comes along, it will act like Firefox and Safari.

  • Hiding Styles from IE 6

     

    It's actually really easy to hide styles from IE 6 but make them visible to standards compliant browsers. Use child selectors. 

    In one design I built, I created a two column layout that required margins and padding. This meant that I was hitting the box model differences when I viewed the page in IE 6. My first CSS style sheet for Firefox included a line like this: 

    div#nav { width: 150px; margin-left: 20px; }

     

    This made the page line up perfectly in Firefox and Safari, but in IE the nav column was pushed over to the right too far. 

    So, I converted the line to use child selectors. The #nav div is a child of the body tag, so I changed the line to read: 

    body > div#nav { width: 150px; margin-left: 20px; }

     

    Of course, doing this made the #nav div lose all it's properties in IE, so I needed to add in some IE styles to get IE 6 looking okay. I added this line to the CSS: 

    #nav { width: 150px; margin-left: 10px; }

     

    The placement of this line of CSS is important if my page is still to look good in Firefox and Safari. The IE line needs to come first. Firefox and Safari will read that line and then it will be over-ridden by the body > div#nav selector lower in the document. IE 6 will read the first line and set the styles. It will then ignore the child selector, as it doesn't recognize them. When IE 7 comes along, it will act like Firefox and Safari.

  • Hiding Styles from IE 6

     

    It's actually really easy to hide styles from IE 6 but make them visible to standards compliant browsers. Use child selectors. 

    In one design I built, I created a two column layout that required margins and padding. This meant that I was hitting the box model differences when I viewed the page in IE 6. My first CSS style sheet for Firefox included a line like this: 

    div#nav { width: 150px; margin-left: 20px; }

     

    This made the page line up perfectly in Firefox and Safari, but in IE the nav column was pushed over to the right too far. 

    So, I converted the line to use child selectors. The #nav div is a child of the body tag, so I changed the line to read: 

    body > div#nav { width: 150px; margin-left: 20px; }

     

    Of course, doing this made the #nav div lose all it's properties in IE, so I needed to add in some IE styles to get IE 6 looking okay. I added this line to the CSS: 

    #nav { width: 150px; margin-left: 10px; }

     

    The placement of this line of CSS is important if my page is still to look good in Firefox and Safari. The IE line needs to come first. Firefox and Safari will read that line and then it will be over-ridden by the body > div#nav selector lower in the document. IE 6 will read the first line and set the styles. It will then ignore the child selector, as it doesn't recognize them. When IE 7 comes along, it will act like Firefox and Safari. 

  • Hiding Styles from IE 6

     

    It's actually really easy to hide styles from IE 6 but make them visible to standards compliant browsers. Use child selectors. 

    In one design I built, I created a two column layout that required margins and padding. This meant that I was hitting the box model differences when I viewed the page in IE 6. My first CSS style sheet for Firefox included a line like this: 

    div#nav { width: 150px; margin-left: 20px; }

     

    This made the page line up perfectly in Firefox and Safari, but in IE the nav column was pushed over to the right too far. 

    So, I converted the line to use child selectors. The #nav div is a child of the body tag, so I changed the line to read: 

    body > div#nav { width: 150px; margin-left: 20px; }

     

    Of course, doing this made the #nav div lose all it's properties in IE, so I needed to add in some IE styles to get IE 6 looking okay. I added this line to the CSS: 

    #nav { width: 150px; margin-left: 10px; }

     

    The placement of this line of CSS is important if my page is still to look good in Firefox and Safari. The IE line needs to come first. Firefox and Safari will read that line and then it will be over-ridden by the body > div#nav selector lower in the document. IE 6 will read the first line and set the styles. It will then ignore the child selector, as it doesn't recognize them. When IE 7 comes along, it will act like Firefox and Safari. 

  • Hiding Styles from IE 6

     

    It's actually really easy to hide styles from IE 6 but make them visible to standards compliant browsers. Use child selectors. 

    In one design I built, I created a two column layout that required margins and padding. This meant that I was hitting the box model differences when I viewed the page in IE 6. My first CSS style sheet for Firefox included a line like this: 

    div#nav { width: 150px; margin-left: 20px; }

     

    This made the page line up perfectly in Firefox and Safari, but in IE the nav column was pushed over to the right too far. 

    So, I converted the line to use child selectors. The #nav div is a child of the body tag, so I changed the line to read: 

    body > div#nav { width: 150px; margin-left: 20px; }

     

    Of course, doing this made the #nav div lose all it's properties in IE, so I needed to add in some IE styles to get IE 6 looking okay. I added this line to the CSS: 

    #nav { width: 150px; margin-left: 10px; }

     

    The placement of this line of CSS is important if my page is still to look good in Firefox and Safari. The IE line needs to come first. Firefox and Safari will read that line and then it will be over-ridden by the body > div#nav selector lower in the document. IE 6 will read the first line and set the styles. It will then ignore the child selector, as it doesn't recognize them. When IE 7 comes along, it will act like Firefox and Safari. 

    By designing for a standards-compliant browser first, and then modifying your CSS to support IE's quirks, you spend a lot less time fiddling with the design and a lot more time

  3 more annotations...

• 27 Oct 08
  

  Designing Web pages is challenging enough without having to build pages that work on every possible combination of Web browser and operating system in existence. So many Web designers choose to take the easy route and design just for the most popular brow

  firefox webdesign web2.0 tutorial reference programming development blog delicious

• 10 May 08
  

  Brian Logan

  webdesign div

• 25 Mar 08
  

  Taufan Aeroperkasa

  css design firefox hack html imported web ie webdesign

• 21 Dec 06
  

  Stuart Maxwell

  css firefox hacks ie webdesign webdev

  • Tips and Tricks to Get Your Site Looking Right in Both Browsers
• 10 Sep 06
  

  Nicole Engard

  css design webdesign

• 29 Aug 06
  

  Nina Scaletti

  How to make your web pages both standards compliant and look good in IE.

  ie design firefox

Would you like to comment?

Join Diigo for a free account, or sign in if you are already a member.