2441 posts
  • Has been a member for 5-6 years
  • Exclusive Author
  • Europe
  • Bought between 10 and 49 items
  • Referred between 100 and 199 users
  • Sold between 100 and 1 000 dollars
  • Envato Studio (Microlancer) Beta Tester
digitalimpact says

So jQuery 2.0 is set to be released early next year, and it will drop support for IE 6 /7/8.

While I couldn’t be happier, how will this affect TF/CC buyers and authors? Is legacy IE support still in high demand? How do you see this impacting your work?

Also, would this mean we get to see IE8 support as optional on the marketplaces at that time?

1673 posts Multimedia Artistry
  • Author had a Free File of the Month
  • Has been a member for 3-4 years
  • Referred between 100 and 199 users
  • Bought between 10 and 49 items
  • Exclusive Author
  • Most Wanted Bounty Winner
  • Elite Author
  • Sold between 100 000 and 250 000 dollars
dnp_theme says

I hope so :)

3192 posts
  • Sold between 5 000 and 10 000 dollars
  • United States
  • Bought between 10 and 49 items
  • Has been a member for 4-5 years
  • Exclusive Author
organicbee says

So jQuery 2.0 is set to be released early next year, and it will drop support for IE 6 /7/8.

While I couldn’t be happier, how will this affect TF/CC buyers and authors? Is legacy IE support still in high demand? How do you see this impacting your work?

Also, would this mean we get to see IE8 support as optional on the marketplaces at that time?

it actually sounds like 1.9 will be released pretty much the same time and still support it, but thats pretty use into forcing people(developers) to drop support

3422 posts
  • Elite Author
  • Sold between 250 000 and 1 000 000 dollars
  • Community Moderator
  • Bought between 100 and 499 items
  • Referred more than 2000 users
  • Has been a member for 4-5 years
  • Repeatedly Helped protect Envato Marketplaces against copyright violations
+4 more
sevenspark Volunteer moderator says

Kinda surprised they’re dropping IE8 . Unless there’s a way to seamlessly fall back to 1.9, I expect that’ll hurt their adoption rate.

2441 posts
  • Has been a member for 5-6 years
  • Exclusive Author
  • Europe
  • Bought between 10 and 49 items
  • Referred between 100 and 199 users
  • Sold between 100 and 1 000 dollars
  • Envato Studio (Microlancer) Beta Tester
digitalimpact says

Unless there’s a way to seamlessly fall back to 1.9, I expect that’ll hurt their adoption rate.

There is one way, but I personally find this method to be stupid. I still need to load jQuery for other browsers:

<!--[if lt IE 9]>
    <script src="jquery-1.9.0.js"></script>
<![endif]-->
<!--[if gte IE 9]><!-->
    <script src="jquery-2.0.0.js"><</script>
<!--<![endif]-->
3192 posts
  • Sold between 5 000 and 10 000 dollars
  • United States
  • Bought between 10 and 49 items
  • Has been a member for 4-5 years
  • Exclusive Author
organicbee says


Unless there’s a way to seamlessly fall back to 1.9, I expect that’ll hurt their adoption rate.

There is one way, but I personally find this method to be stupid. I still need to load jQuery for other browsers:

<!--[if lt IE 9]>
    <script src="jquery-1.9.0.js"></script>
<![endif]-->
<!--[if gte IE 9]><!-->
    <script src="jquery-2.0.0.js"><</script>
<!--<![endif]-->
<![if !IE]>
    <script src="jquery-2.0.0.js"><</script>
<!--<![endif]-->

there is an if not IE conditional

3422 posts
  • Elite Author
  • Sold between 250 000 and 1 000 000 dollars
  • Community Moderator
  • Bought between 100 and 499 items
  • Referred more than 2000 users
  • Has been a member for 4-5 years
  • Repeatedly Helped protect Envato Marketplaces against copyright violations
+4 more
sevenspark Volunteer moderator says


Unless there’s a way to seamlessly fall back to 1.9, I expect that’ll hurt their adoption rate.

There is one way, but I personally find this method to be stupid. I still need to load jQuery for other browsers:

<!--[if lt IE 9]>
    <script src="jquery-1.9.0.js"></script>
<![endif]-->
<!--[if gte IE 9]><!-->
    <script src="jquery-2.0.0.js"><</script>
<!--<![endif]-->

Right, but you’d still need a way to be able to use new 2.0 functions, and not have them blow up in 1.9. That’s the difficult (impossible?) issue.

In other words, loading the proper script isn’t difficult; making sure your own scripts run seamlessly no matter which library loads is … well I can’t think of any way of doing it myself, unless 1.9 contained all 2.0 functions (which seems bass-ackwards).

by
by
by
by
by
by