1149 posts
  • Affiliate Level 1
  • Author Level 3
  • Beta Tester
  • Collector Level 2
+3 more
fillerspace
says

I’ve noticed that Modernizr adds a “no-cssgradients” class for IE when IE supports gradients using a filter declaration. So I end up having to target IE specifically as well.

2952 posts
  • 6 Years of Membership
  • Affiliate Level 5
  • Author Level 8
  • Bundle Boss
+12 more
DDStudios
says

By the way guys I’m looking for someone to fix my latest theme for IE 7 -8 :)

It’s a paid job so if you are interested, email me at : ddwebstudios [at] hotmail [dot] com

I’ll show you the theme.

194 posts
  • 5 Years of Membership
  • Author Level 7
  • Collector Level 4
  • Elite Author
+4 more
digitonik
says

By the way guys I’m looking for someone to fix my latest theme for IE 7 -8 :)

It’s a paid job so if you are interested, email me at : ddwebstudios [at] hotmail [dot] com

I’ll show you the theme.

Just sent you an email. I may be able to help depending on how long it will take.

597 posts
  • Author Level 12
  • Freebie
  • Collector Level 2
  • Winner
+21 more
theMOLITOR
says

Styling Different Versions of IE in a Single CSS File: http://tinyurl.com/476ac5w

1149 posts
  • Affiliate Level 1
  • Author Level 3
  • Beta Tester
  • Collector Level 2
+3 more
fillerspace
says

Styling Different Versions of IE in a Single CSS File: http://tinyurl.com/476ac5w

I’m not a fan of breaking validation for compatibility. Here’’s what I do:

<!--[if lt IE 7 ]> <html lang="en-us" class="ie6"> <![endif]-->
<!--[if IE 7 ]>    <html lang="en-us" class="ie7"> <![endif]-->
<!--[if IE 8 ]>    <html lang="en-us" class="ie8"> <![endif]-->
<!--[if IE 9 ]>    <html lang="en-us" class="ie9"> <![endif]-->   
<!--[if (gt IE 9)|!(IE)]><!--> <html class="non-ie" lang="en-us"> <!--<![endif]-->
</html>

Then in my CSS :

div {background:#AAA;}
.ie6 div {background:#000;}
.ie7 div {background:#111;}
.ie8 div {background:#222;}
.ie9 div {background:#333;}

I also have a custom browser detection library that assigns classes to the other browsers so I can also do this (in rare cases):

.webkit div {background:#BBB;}
.safari div {background:#000;}
.firefox3 div {background:#111;}
.firefox3_6 div {background:#111;}
.firefox3_6_1_3 div {background:#222;} /*this one is so crazy I'd never do it*/
.opera11 div {background:#333;}

For cases like these, I prefer to do feature detection with Modernizr, especially for things like css gradients or columns, but sometimes you find that certain browsers are just off by a few pixels for no good reason. That’s when it’s nice to say “move this up 3px just for Opera 11”

597 posts
  • Author Level 12
  • Freebie
  • Collector Level 2
  • Winner
+21 more
theMOLITOR
says

I’m not a fan of breaking validation for compatibility.

If you’re using CSS3 (as you should), you’re breaking validation anyways. Besides, you should only be concerned about HTML validation, not CSS validation.

251 posts
  • 5 Years of Membership
  • Affiliate Level 1
  • Author Level 4
  • Beta Tester
+5 more
web_gab
says

Perhaps we should help landonw develop his magic wand for IE by sharring IE problems. I personally think this is a great idea if it will be materialized: http://themeforest.net/forums/thread/magic-wand-for-ie/40705

1149 posts
  • Affiliate Level 1
  • Author Level 3
  • Beta Tester
  • Collector Level 2
+3 more
fillerspace
says


I’m not a fan of breaking validation for compatibility.
If you’re using CSS3 (as you should), you’re breaking validation anyways. Besides, you should only be concerned about HTML validation, not CSS validation.

I totally agree…maybe validation wasn’t the right word. I don’t particularly care that some online tool says my code validates. What I meant was introducing non-semantic declarations like *background or _background to me is sloppy. .ie7 div {background: #000} is much cleaner, and it is logical for the next person maintaining it.

by
by
by
by
by
by