Link Details

Link 503493 thumbnail
User 259551 avatar

By fuzzer
via css3wizardry.com
Published: Oct 20 2010 / 02:37

Comments

Add your comment
User 792975 avatar

armed replied ago:

1 votes Vote down Vote up Reply

The only good thing about IE is that it continues to loose it's positions :)

User 295190 avatar

ThePeach replied ago:

0 votes Vote down Vote up Reply

as someone else already said somewhere else, I just hope this won't stop people moving away from ie6 :)
Btw, as the author of the article said, that could no longer be true, the step forward IE did, from a web developer point of view is huge.

User 366080 avatar

thelizardreborn replied ago:

0 votes Vote down Vote up Reply

Pretty sure IE9 will not impact people moving away from IE6 at all. From what I understand, IE9 doesn't run on any OS before Vista, and IE6 certainly isn't running on any systems newer than XP.

User 209172 avatar

mcnaz replied ago:

0 votes Vote down Vote up Reply

How very sad... now we develop sites we have to cater for IE6, IE7, IE8 and (FF, Chrome, Safari which count as one browser because these three Just Work). What an utter waste of our time.

User 393686 avatar

RawThinkTank replied ago:

1 votes Vote down Vote up Reply

They could not beat JQuery so now they are taking it out on CSS

User 464161 avatar

cstrosser replied ago:

0 votes Vote down Vote up Reply

No code included in article.

I use tons of CSS3 in my applications, and the differences between IE9 and Firefox have been minimal. I have more trouble between Firefox and Chrome than FF and IE9. This is just more IE bashing from the same old people. While I'm not particularly fond of IE9, this is elitism at its best.

User 371439 avatar

nikki9696 replied ago:

0 votes Vote down Vote up Reply

Who cares what the code is, when MS is touting that their new and shiny model can render the SAME as other browsers? Which code was used is irrelevant for the purposes of demonstrating that statement to be woefully incorrect.

User 464161 avatar

cstrosser replied ago:

1 votes Vote down Vote up Reply

The code is absolutely relevant. I can create something in a few minutes which would look good in FF but not Chrome, or Chrome but not FF. It's not that hard to accomplish.

A good web developer would not jump to conclusions about flimsy assumptions made without providing any documentation or proof. If the blogger posted the source code for examination, we would be having a different conversation, but he has not.

Add your comment


Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.

Java EE7
Written by: Andrew Lee Rubinger
Featured Refcardz: Top Refcardz:
  1. Design Patterns
  2. OO JS
  3. Cont. Delivery
  4. CI Patterns
  5. CI Tools
  1. Spring Integration
  2. Git
  3. Regex
  4. Java
  5. REST