- Sold between 100 and 1 000 dollars
- Has been a member for 3-4 years
- Bought between 10 and 49 items
- Exclusive Author
- Microlancer Beta Tester
- United States
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.
- Attended a Community Meetup
- Australia
- Author had a File in an Envato Bundle
- Author had a Free File of the Month
- Author was Featured
- Bought between 100 and 499 items
- Contributed a Blog Post
- Exclusive Author
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.
- Author was Featured
- Bought between 100 and 499 items
- Exclusive Author
- Has been a member for 3-4 years
- Sold between 50 000 and 100 000 dollars
- United States
DDStudios said
By the way guys I’m looking for someone to fix my latest theme for IE 7 -8It’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.
- United States
- Sold between 250 000 and 1 000 000 dollars
- Featured in a Magazine
- Won a Competition
- Was featured in a podcast
- Author was Featured
- Item was Featured
- Beta Tester
Styling Different Versions of IE in a Single CSS File: http://tinyurl.com/476ac5w
- Sold between 100 and 1 000 dollars
- Has been a member for 3-4 years
- Bought between 10 and 49 items
- Exclusive Author
- Microlancer Beta Tester
- United States
themolitor said
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”
- United States
- Sold between 250 000 and 1 000 000 dollars
- Featured in a Magazine
- Won a Competition
- Was featured in a podcast
- Author was Featured
- Item was Featured
- Beta Tester
fillerspace said
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.
- Beta Tester
- Bought between 10 and 49 items
- Exclusive Author
- Has been a member for 3-4 years
- Microlancer Beta Tester
- Referred between 1 and 9 users
- Romania
- Sold between 5 000 and 10 000 dollars
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
- Sold between 100 and 1 000 dollars
- Has been a member for 3-4 years
- Bought between 10 and 49 items
- Exclusive Author
- Microlancer Beta Tester
- United States
themolitor said
fillerspace saidIf 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’m not a fan of breaking validation for compatibility.
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.
Request processing...