- Author was Featured
- Item was Featured
- Sold between 10 000 and 50 000 dollars
- Microlancer Beta Tester
- Has been a member for 0-1 years
- Referred between 10 and 49 users
- Bought between 10 and 49 items
- India
- Exclusive Author
Starting in jQuery 1.8, special builds can now be created that optionally exclude or include any of the following modules:
- ajax
- css
- dimensions
- effects
- offset
- United Kingdom
- Community Superstar
- Attended a Community Meetup
- Repeatedly Helped protect Envato Marketplaces against copyright violations
- Sold between 5 000 and 10 000 dollars
- Has been a member for 2-3 years
- Microlancer Beta Tester
- Bought between 100 and 499 items
- Referred between 10 and 49 users
IE being removed, Great! Even more reason for people to move away from it.
- Exclusive Author
- Sold between 10 000 and 50 000 dollars
- Item was Featured
- Has been a member for 3-4 years
- Bought between 1 and 9 items
- Portugal
Good news for the jquery users 
IE version lower than 9 will start to be marginalized, developers can’t be developing innovating things taking in consideration archaic browsers too much longer. I wouldn’t test a desktop application on a windows 98 so why test a site on IE6 ?
- Bought between 100 and 499 items
- Exclusive Author
- Has been a member for 4-5 years
Supposedly, in jQuery v1.9 IE 6 /7/8 will still be supported but will be identical otherwise compared to the 2.0 version. I imagine it’ll be a while before v2.0 is used widely if this is the case with the 1.9 version. The fact that there’ll be a choice is both bad and good.
- Argentina
- Sold between 50 000 and 100 000 dollars
- Author was Featured
- Author had a Free File of the Month
- Most Wanted Bounty Winner
- Bought between 50 and 99 items
- Referred between 50 and 99 users
- Microlancer Beta Tester
- Exclusive Author
plusquare said
Good news for the jquery users
+1000000000 
- Sold between 100 000 and 250 000 dollars
- Author was Featured
- Item was Featured
- Most Wanted Bounty Winner
- Bought between 10 and 49 items
- Exclusive Author
- Referred between 50 and 99 users
- Has been a member for 2-3 years
plusquare said
developers can’t be developing innovating things taking in consideration archaic browsers too much longer.
Completely agree!
- Author was Featured
- Item was Featured
- Sold between 10 000 and 50 000 dollars
- Microlancer Beta Tester
- Has been a member for 0-1 years
- Referred between 10 and 49 users
- Bought between 10 and 49 items
- India
- Exclusive Author
plusquare saidThe best thing I’ve heard in a week..
I wouldn’t test a desktop application on a windows 98 so why test a site on IE6 ?
- United States
- Has been a member for 4-5 years
- Exclusive Author
- Author was Featured
- Sold between 50 000 and 100 000 dollars
- Item was Featured
- Contributed a Tutorial to a Tuts+ Site
- Author had a Free File of the Month
The general public was educated about Flash not being available, so I don’t see why they can’t be educated about the fact that their browser sucks. jQuery 2.0 should just include an automatic “your browser is old” message. That would be fantastic
- Exclusive Author
- Sold between 10 000 and 50 000 dollars
- Item was Featured
- Has been a member for 3-4 years
- Bought between 1 and 9 items
- Portugal
CodingJack said
The general public was educated about Flash not being available, so I don’t see why they can’t be educated about the fact that their browser sucks. jQuery 2.0 should just include an automatic “your browser is old” message. That would be fantastic
Exactly, like flash does when you have an old flash version ahah
- Sold between 50 000 and 100 000 dollars
- Repeatedly Helped protect Envato Marketplaces against copyright violations
- Microlancer Beta Tester
- Exclusive Author
- Has been a member for 3-4 years
- Europe
- Referred between 10 and 49 users
- Bought between 50 and 99 items
The sizzle looks more strict, I’ve caught some kind of error with prettyPhoto and 1.8. It’s great that it now throws more meaningful errors in the console, but it’s still a challenge to debug it way back to where something was originally called. And also, was it throwing errors and reloading the page when one of the data values was missing in an ajax request? In case you forgot to validate/check data beforehand… link
