JQuery 2.0 Drops Support for IE6/7/8; API-Compatible with jQuery 1.9.
51–60 of 237 posts
Re: JQuery 2.0 Drops Support for IE6/7/8; API-Compatible with jQuery 1.9.
#52Earlier quoted context omitted.
It's pretty simple– if you want to support IE<9, don't upgrade to jQuery 2.x. A lot of people are already dropping support for IE<8.
It's really not that simple. Now you have to check to see if a plugins support 1.9 or 2.0, and plugin writers will have to support both or IE8 supporters will have to live without new plugins.
Re: JQuery 2.0 Drops Support for IE6/7/8; API-Compatible with jQuery 1.9.
#53Isn't one of the reasons for jquery to "abstract away" the differences between browsers so I don't have to worry about it? Dropping support for popular browsers doesn't seem to help me much.
And the corporate clients could finally get through their heads it is not ok to expect employees to be accessing the internet through IE. Businesses don't have the rights to stick their fingers in their ears singing 'lalala' while the internet attempts to grow around the tumour of conditional comments and other crap.
Re: JQuery 2.0 Drops Support for IE6/7/8; API-Compatible with jQuery 1.9.
#54Re: JQuery 2.0 Drops Support for IE6/7/8; API-Compatible with jQuery 1.9.
#55I'll play the cynic here and try to diagnose why this is even being considered. jQuery is a very invasive API. Its goal is to steal all the work from the developer, and to "guarantee" what it deems to be "correct" input for a certain subset of browsers. This approach may ostensibly work, but inevitably falls apart, which leads to thousands of "bugs" being reported. Because the API has grown to be so massive, goalpost…
Re: JQuery 2.0 Drops Support for IE6/7/8; API-Compatible with jQuery 1.9.
#56Sorry, but this is a disaster. Dropping support for IE6 may be OK, IE7 is a bit too soon, but IE8? I haven't tested my stuff on IE6 and IE7 for a long time, but I still do it on IE8 everyday. It was released in 2009! And it's decent enough, PNG transparencies, etc. jQuery's main raison d'être might have gone out the window.
Re: JQuery 2.0 Drops Support for IE6/7/8; API-Compatible with jQuery 1.9.
#57I don't know if I can get behind this or not. I understand their desire but I don't see this as a viable option just yet. I'm not so concerned with 2.0 and 1.9 as you can load the right one, but what about when 2.1 comes out? Are they going to back-port all the new features to 1.9.1? If not then I now have a big fragmentation issue if I rely on anything specific to 2.1. Don't forget that IE 8 is the last version XP w…
>JQuery has just set a time limit on proper web access for an entire OS. doesnt chrome work on xp?
Re: JQuery 2.0 Drops Support for IE6/7/8; API-Compatible with jQuery 1.9.
#58So does this mean that there will be ongoing development in the 1.9 line which will add new features available in the 2.0 line, or is this just the end of the line for IE If that's true, this seems like an odd line in the sand for them to draw. IE9 isn't available before Win7, so it can't die until users upgrade their OS. According to StatCounter[1], IE8 still represents 13.78% of Worldwide visits (plus 1.4% for IE7;…
Re: JQuery 2.0 Drops Support for IE6/7/8; API-Compatible with jQuery 1.9.
#59Sorry, but this is a disaster. Dropping support for IE6 may be OK, IE7 is a bit too soon, but IE8? I haven't tested my stuff on IE6 and IE7 for a long time, but I still do it on IE8 everyday. It was released in 2009! And it's decent enough, PNG transparencies, etc. jQuery's main raison d'être might have gone out the window.
Yep, it's ancient. Chrome and Firefox are on average about 3 weeks old. IE8 is over 50 times older.
>jQuery's main raison d'être might have gone out the window.
Normalization was just one part. It still provides a much nicer API. There are also events, AJAX, effects, and some useful helpers.
[].slice.call(document.querySelectorAll('p')).forEach(function (el) {console.log(el);});
vs $('p').each(function () {console.log(this);});Re: JQuery 2.0 Drops Support for IE6/7/8; API-Compatible with jQuery 1.9.
#60I don't know if I can get behind this or not. I understand their desire but I don't see this as a viable option just yet. I'm not so concerned with 2.0 and 1.9 as you can load the right one, but what about when 2.1 comes out? Are they going to back-port all the new features to 1.9.1? If not then I now have a big fragmentation issue if I rely on anything specific to 2.1. Don't forget that IE 8 is the last version XP w…
The cycle here is pretty long: jQuery 2.0 will be released in "Early 2013". For some time (probably at least 6 months if not longer), jQuery 1.9 and 2.x will be perfectly API compatible. That means that the conditional comment approach will work with very little downside. That gets us to summer or Fall 2013. At this point, there may be a release of jQuery 2.1. According to the blog post, it will probably contain few…
It better grow pretty fast. By late 2012, jQuery will still be supporting a browser released in 2001 but by early 2013 it won't support a browser that was only replaced by MS in 2011.
Corporate America is not IE8's only domain. There are a lot of people who don't even know what a browser is. And IE8 was the default browser on Windows 7.