2468 posts
  • 6 Years of Membership
  • Author Level 2
  • Affiliate Level 4
  • Beta Tester
+3 more
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?

1899 posts Multimedia Artistry
  • Elite Author
  • 4 Years of Membership
  • Freebie
  • Most Wanted Winner
+4 more
dnp_theme
says

I hope so :)

3439 posts
  • Author Level 4
  • Collector Level 2
  • Community Superstar
  • United States
+2 more
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

3535 posts
  • Power Elite Author
  • Author Level 12
  • Trendsetter
  • United States
+13 more
sevenspark
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.

2468 posts
  • 6 Years of Membership
  • Author Level 2
  • Affiliate Level 4
  • Beta Tester
+3 more
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]-->
3439 posts
  • Author Level 4
  • Collector Level 2
  • Community Superstar
  • United States
+2 more
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

3535 posts
  • Power Elite Author
  • Author Level 12
  • Trendsetter
  • United States
+13 more
sevenspark
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