1026 posts
  • Sold between 100 000 and 250 000 dollars
  • Elite Author
  • France
  • Author had a File in an Envato Bundle
  • Author had a Free File of the Month
  • Contributed a Tutorial to a Tuts+ Site
  • Repeatedly Helped protect Envato Marketplaces against copyright violations
+4 more
Pixelworkshop says

Hi there !

Just wanted your opinion about CSS3 and old browsers (well, IE…). I received quite a few emails concerning my stuff on Codecanyon from customers who wanted a CSS3 item look exactly the same with all browsers : gradients, rounded corners, etc.

What do you usually do ? A simple CSS fallback for IE or do you use some scripts like PIE , selectivizr, or this one ?

99 posts
  • Bought between 1 and 9 items
  • Referred between 1 and 9 users
  • Belgium
  • Sold between 10 000 and 50 000 dollars
  • Exclusive Author
  • Has been a member for 3-4 years
Lamovo says

What do you usually do ? A simple CSS fallback for IE or do you use some scripts like PIE , selectivizr, or this one ?

More than including a fallback script like those you mentioned is a waist of time. There’s something wrong if you need to spend 80% of your time into making it work for one browser vendor if all other browsers only need 20% time to make it right.

As long as the item works in those microsoftified browsers, it’s okay. Let the users with real browsers benefit the awesomeness of CSS3 .

Webdesign will never be exactly the same. Different platforms, different browsers, different release schedules and devices like ipads make this very unlikely. Clients should understand that we can only make something behave or look right in the majority of leading browsers.

730 posts
  • Elite Author
  • Attended a Community Meetup
  • Has been a member for 4-5 years
  • Sold between 100 000 and 250 000 dollars
  • Bought between 50 and 99 items
  • Exclusive Author
  • Most Wanted Bounty Winner
+2 more
mordauk says

I’ve used this one, which creates images for you based upon your CSS for older browsers. It works really well.

1026 posts
  • Sold between 100 000 and 250 000 dollars
  • Elite Author
  • France
  • Author had a File in an Envato Bundle
  • Author had a Free File of the Month
  • Contributed a Tutorial to a Tuts+ Site
  • Repeatedly Helped protect Envato Marketplaces against copyright violations
+4 more
Pixelworkshop says


What do you usually do ? A simple CSS fallback for IE or do you use some scripts like PIE , selectivizr, or this one ?

More than including a fallback script like those you mentioned is a waist of time. There’s something wrong if you need to spend 80% of your time into making it work for one browser vendor if all other browsers only need 20% time to make it right.

As long as the item works in those microsoftified browsers, it’s okay. Let the users with real browsers benefit the awesomeness of CSS3 .

Webdesign will never be exactly the same. Different platforms, different browsers, different release schedules and devices like ipads make this very unlikely. Clients should understand that we can only make something behave or look right in the majority of leading browsers.

I totally understand your point of view, I avoid supporting IE as much as possible, but now, I’m preparing an item for Codecanyon and I’m thinking that if I don’t do it now, I’ll maybe have to sooner or later.

@mordauk nice link, I’ll give it to my customers :)

68 posts
  • Bought between 10 and 49 items
  • Exclusive Author
  • Has been a member for 5-6 years
  • Referred between 10 and 49 users
  • Sold between 10 000 and 50 000 dollars
spotnil says

in my opinion a clear note of what is not supported in the older browsers should be enough. Once when they are warned they can make a decision to buy a CSS3 or not to buy.

But it is tough decision from an author point of view because not supporting older browsers probably reduces the number of the potential clients.

A useful site to me is http://css3please.com/

Good luck!

by
by
by
by
by
by